Jira
Connect Jira so issues, boards, sprints, comments, and priorities can feed planning and updates.
If Jira stays as the execution source, we add roadmap context, recaps, standups, blocker review, stakeholder updates, and AI handoff without forcing a full migration first.
What Jira adds
Jira issues can appear in recap, boards, issue lists, and triage. Issue context can also help AI derive completed work from commits, pull requests, comments, and other captured activity.
Assigned Jira issues appear in Planned when they are in progress, in review, or in open sprints and have recent activity. This keeps daily planning focused on current sprint work instead of stale tickets.
Inline issue work
Open a Jira issue from the workspace to edit title, description, status, priority, and assignees without switching tools. Changes stay synchronized with Jira.
Status and priority options come from the Jira project configuration. Assignee choices follow Jira's Assignable User permission for the project.
Jira issues are fetched when you open the view, then cached. Refresh the recap or issue list when you need the latest source state.
Already using Jira?
Jira is useful when issue tracker status needs to become part of team planning, standups, daily recaps, blocker review, and stakeholder reporting.
Jira issues can appear in Recaps, Boards, and Triage. They also give AI more context when it determines completed work from commits, pull requests, comments, and other captured activity.
If the team later wants this workspace to own more planning, create Initiatives for planned work first. Keep issue-level execution in Jira where it still helps. For completed-work behavior, see Captured Work.