Jira issue process: see which status each issue waits in longest

What does Duaer read from Jira?

One source reads one project. Each issue is a case: Created, then each status it moves to, named as in the project, such as In Progress, In Review or Done. The issue type, priority and assignee come with it.

Workflows differ per project, so no process template is applied; the map, boards and findings work as usual.

How do you connect Jira to Duaer?

1. Prepare an Atlassian account that can browse the project (Browse projects permission) and create an API token.
2. In Duaer, create a Jira Software Cloud API credential with the email, the API token and the site address (like https://acme.atlassian.net). Knowledge search uses this kind of credential too.
3. As an owner or admin, open Data sources, select Add source, choose Jira under Chat, mail and work, choose the credential, select Load projects, choose a project and confirm.

How often does it read, and how much?

Each run reads the issues changed since the last one by their last update, 50 at most, with their whole change log; a first read covers all issues and finishes over several runs. A step is never written twice. Read only: Duaer never changes anything in Jira.

What are the limits?

• Jira Cloud only.
• Each source reads one project; add one per project.
• The endpoints and fields follow Atlassian’s published documentation and are not yet checked against a real site; the first real read may need adjustments.