JiraSettings
| Setting | What it is |
|---|---|
| ConnectionRequired | The Jira connection the step signs in with. |
| JQLRequired | Jira refuses a query that is not bounded — one that is only an ORDER BY names no issues and is rejected. An ORDER BY may name at most 7 fields. |
| Fields to fetch | Jira returns nothing you do not ask for. |
| Expand | text |
| Name custom fields by their key | true/false |
| Include archived projects | true/false |
| Issues per call | 1 to 100. |
| Fetch every page | Follows Jira's next-page token until it stops sending one. At Pages at most or 5,000 issues it stops and answers the token to continue from. A token expires after 7 days, so one carried across a parked run is dead. |
| Pages at most | 1 to 100. |
| Also count the matches | Jira no longer returns a total from a search, so this costs one extra call and the number it gives is approximate. |
| Cursor | Paste a previous run's Next cursor to read the page after it. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `jira`) |
jql | text |
fields | text, by default "summary,status,assignee,priority,updated" |
expand | text |
fieldsByKeys | true/false, by default false |
includeArchivedProjects | true/false, by default false |
limit | number, by default 50 |
returnAll | true/false, by default false |
maxPages | number, by default 20used when `returnAll` is true |
withCount | true/false, by default false |
cursor | text |
Output
| Field | Type |
|---|---|
issues | array |
issueCountIssues in this answer | number |
hasMoreMore issues are waiting behind this page | boolean |
nextPageJira's token for the next page | string |
approximateTotalAbout how many match (when asked for) | number |
pagesRequests this read took | number |
nextCursorCursor for the next page | string |
Sample output, and the expression for each field
- approximateTotal0
- hasMorefalse
- issueCount0
- issues[]
- nextPage""
- pages1
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": "",
"expand": "",
"fields": "summary,status,assignee,priority,updated",
"fieldsByKeys": false,
"includeArchivedProjects": false,
"jql": "<jql>",
"limit": 50,
"maxPages": 20,
"returnAll": false,
"withCount": false
},
"label": "Search issues",
"type": "jira.searchIssues",
"version": 2
}Older versions
A flow that already has this version keeps running it. A new step always gets the newest.
Version 1
| Setting | What it is |
|---|---|
| ConnectionRequired | The Jira connection the step signs in with. |
| JQLRequired | Jira refuses a query that is not bounded — one that is only an ORDER BY names no issues and is rejected. An ORDER BY may name at most 7 fields. |
| Fields to fetch | Jira returns nothing you do not ask for. |
| Expand | text |
| Name custom fields by their key | true/false |
| Include archived projects | true/false |
| Issues per call | 1 to 100. |
| Fetch every page | Follows Jira's next-page token until it stops sending one. At Pages at most or 5,000 issues it stops and answers the token to continue from. A token expires after 7 days, so one carried across a parked run is dead. |
| Pages at most | 1 to 100. |
| Also count the matches | Jira no longer returns a total from a search, so this costs one extra call and the number it gives is approximate. |
Technical details
| Key | Value |
|---|---|
connection | texta connection id from `requires.connections` (provider `jira`) |
jql | text |
fields | text, by default "summary,status,assignee,priority,updated" |
expand | text |
fieldsByKeys | true/false, by default false |
includeArchivedProjects | true/false, by default false |
limit | number, by default 50 |
returnAll | true/false, by default false |
maxPages | number, by default 20used when `returnAll` is true |
withCount | true/false, by default false |