FlowmageDocs

Find users

BetaReads dataVersion 2

Finds Jira users, or the people who can be assigned an issue.

Settings

SettingWhat it is
ConnectionRequiredThe Jira connection the step signs in with.
Who to look through"all" or "assignable"
Name or e-mail containsJira Cloud identifies a person by account id; an e-mail address is often hidden by that person's Atlassian privacy setting, so a search on an address can legitimately find nobody.
Project keyPicked from the list Jira offers.
Issue keyEither a project key or an issue key — Jira needs one of the two.
People per call1 to 100.
Fetch every pageWalks Jira's offset pages, and refuses past 5,000 people.
CursorPaste a previous run's Next cursor to read the page after it.
Technical details
KeyValue
connectiontexta connection id from `requires.connections` (provider `jira`)
scope"all" or "assignable", by default "all"
querytext
projecttexta value from the vendor's own list; used when `scope` is "assignable"
issuetextused when `scope` is "assignable"
limitnumber, by default 50
returnAlltrue/false, by default false
cursortext

Output

FieldType
usersPeoplearray
userCountPeople in this answernumber
accountIdsDisplay name → account idobject
hasMoreMore people are waiting behind this pageboolean
nextCursorCursor for the next pagestring
Sample output, and the expression for each field
  • accountIds{}
  • hasMorefalse
  • userCount0
  • users[]

Errors

When a step of this node stops a run, the run page shows a code. Look it up:

Example step

The step as a flow file holds it. Replace each value in <…>.

{
  "config": {
    "connection": "<connection id>",
    "cursor": "",
    "issue": "",
    "limit": 50,
    "project": "",
    "query": "",
    "returnAll": false,
    "scope": "all"
  },
  "label": "Find users",
  "type": "jira.findUsers",
  "version": 2
}

Older versions

A flow that already has this version keeps running it. A new step always gets the newest.

Version 1
SettingWhat it is
ConnectionRequiredThe Jira connection the step signs in with.
Who to look through"all" or "assignable"
Name or e-mail containsJira Cloud identifies a person by account id; an e-mail address is often hidden by that person's Atlassian privacy setting, so a search on an address can legitimately find nobody.
Project keyPicked from the list Jira offers.
Issue keyEither a project key or an issue key — Jira needs one of the two.
People per call1 to 100.
Fetch every pageWalks Jira's offset pages, and refuses past 5,000 people.
Technical details
KeyValue
connectiontexta connection id from `requires.connections` (provider `jira`)
scope"all" or "assignable", by default "all"
querytext
projecttexta value from the vendor's own list; used when `scope` is "assignable"
issuetextused when `scope` is "assignable"
limitnumber, by default 50
returnAlltrue/false, by default false