Type: Function
Function: NOT_INCLUDE_ME
Syntax: NOT_INCLUDE_ME(usernames)
Description: Returns true if the list of usernames contains none of the current user's usernames.
The current user is the person viewing the insight. Through the Keypup API or the MCP server, it is the person the API token or the MCP connection belongs to.
NOT_INCLUDE_ME(usernames) is the same as NOT(CONTAINS(usernames, ME())): see ME.
It is the same condition as the does not include me filter of the insight designer (see Using filters). Use it in a custom formula, to count, group or label records on that condition, or as a filter in a query sent through the Keypup API or MCP server.
Usernames are matched as text. A user's usernames are the ones of the apps they connected to their Keypup account (see Managing app identities), one per app. Someone else with the same username in another app, or with the same display name in an app which identifies people by name, such as Jira or Bitbucket, also matches. A user with no app connected matches nothing. The does not include me filter of the insight designer matches the user's accounts exactly: prefer it when building an insight.
Sample usage:
NOT_INCLUDE_ME(requested_reviewer_usernames)returnstruefor the pull requests the current user is not a requested reviewer of.