How can I modify our Jira workflow steps to include a client review stage without breaking all our existing automation rules
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
How can I modify our Jira workflow steps to include a client review stage without breaking all our existing automation rules
2 real searches · 1 real-search pass
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (2)
Classes come from the query-classifier (a local Laya model). 2 of 2 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT2 real searches · gpt-6
Atlassian Jira Cloud edit workflow add status transition automation rules status changed trigger documentation Google ↗
Atlassian Jira automation rule status transition trigger conditions workflow changes documentation Google ↗
- Jira automation triggers | Cloud automation Cloud · support.atlassian.com
- Create automation flows in Jira | Cloud automation Cloud · support.atlassian.com
- Create workflow transitions · support.atlassian.com
- Edit a workflow's rules · support.atlassian.com
Queries
2 queries · click a column to sort
| Query / type | Search | Intent | Query class | Routing format | Cluster | Freq ↓ | Weight |
|---|---|---|---|---|---|---|---|
Atlassian Jira Cloud edit workflow add status transition automation rules status changed trigger documentation OBSERVED | Google ↗ AI Mode ↗ | — | Instruction | — | — | 1x of 1 | |
Atlassian Jira automation rule status transition trigger conditions workflow changes documentation OBSERVED | Google ↗ AI Mode ↗ | — | Consequence | — | — | 1x of 1 |