Type: Function
Function: NOT_INCLUDE_USER
Syntax: NOT_INCLUDE_USER(usernames, "<user id>")
Description: Returns true if the list of usernames contains none of the user's usernames.
The user is given by their Keypup user ID, written as text, and must be a member of the team. To find your teammates' IDs, run { companies { nodes { name users { nodes { id firstName email } } } } } on the HQ API of the API Explorer (see Using the API). In the insight designer, the is user filter lets you pick the person by name instead.
NOT_INCLUDE_USER(usernames, "<user id>") is the same as NOT(CONTAINS(usernames, USERNAMES("<user id>"))): see USERNAMES.
It is the same condition as the does not include user 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 user filter of the insight designer matches the user's accounts exactly: prefer it when building an insight.
Sample usage:
NOT_INCLUDE_USER(requested_reviewer_usernames, "<user id>")returnstruefor the pull requests the user is not a requested reviewer of.