Your project management software
Jira
Jira, made by Atlassian, is listed here as project management software.
Jira is Atlassian's tool for tracking work, kept as work items inside spaces (still called projects in some places). Every work item has a work type: software spaces start with Epic, Story, Task, Bug and Subtask, business spaces with Task and Subtask, and the default hierarchy runs from epics through standard items down to subtasks, with extra levels on the Premium and Enterprise plans. Teams move work items through workflows they configure, see them on boards and a timeline, run sprints, and search with Jira Query Language (JQL); it belongs to the same Atlassian family as Confluence, Loom and Jira Service Management, whose service spaces add work types such as Incident and Service request.
What it lets a workflow do
Every workflow template below works from what Jira gives it and changes nothing in Jira.
Workflows that use it
No workflow template names Jira yet. These are written for project management software, not for Jira by name.
Project lessons review Workflow template
Works from an export from project management software.
Can see: the deliverables list: original scope and what happened to each. Can change: nothing.
Roadmap tradeoff review Workflow template
Works from an export from project management software.
Can see: roadmap items with team, status, window, effort and dependencies. Can change: nothing.
Scope change impact review Workflow template
Works from an export from project management software.
Can see: working list of deliverables with status. Can change: nothing.
Three-week look-ahead constraint review Workflow template
Works from an export from project management software.
Can see: schedule export with activities, trades and dates. Can change: nothing.
Teams whose workflow templates use project management software:
How it connects
Each connector below is one we know of, with who publishes it, where and when we found it, and its trust level.
Published by its maker
Connector from the maker of Jira
A connector an AI assistant can use.
Published by Atlassian, as the maker's own page states.
Found in the maker's own documentation on 11 November 2026. Last checked on 12 November 2026.
ListedFound in a named public source on a stated date. We have not reviewed or used it.
Programming interface from the maker of Jira
A programming interface for software developers.
Published by Atlassian, as the maker's own page states.
Found in the maker's own documentation on 12 November 2026. Last checked on 12 November 2026.
ListedFound in a named public source on a stated date. We have not reviewed or used it.
What setup takes, and who approves it
Connecting a workflow to Jira is agreed when the work is scoped: a person who looks after Jira at your company approves how the workflow signs in and what it may see and change.
No time is promised here. Where no connector exists, the workflow works from an export.
What was checked, and when
- The maker's own pages: read on 12 November 2026.
- The workflow templates above: each link was read from the template's own text and reviewed, most recently on 12 November 2026.
Next step
Want a workflow above built for your team? Open it and choose how to start, or book a fit call.
Technical details
- Atlassian Rovo MCP Server · MCP serverFound in the maker's own documentation
https://mcp.atlassian.com/v2/mcpAtlassian's developer page describes a cloud-hosted MCP server that connects AI clients to Atlassian Cloud apps, with Jira listed among the supported apps.The maker’s page - Jira Cloud platform REST API · Public APIFound in the maker's own documentation
https://your-domain.atlassian.net/rest/api/Atlassian's developer page describes calling the Jira REST APIs on a Jira site's own address, and gives the path pattern for them.The maker’s page