Delivery
- Delivery
- Category
- OAuth
- Connection
- Boards you invite
- Lands in memory
What agents do
The work that stays in Jira.
Read the ticket and who is blocked
Status, comments, and the person waiting land next to the decision that created the work.
Draft the comment or the transition
Mor proposes the update. Jira does not change until you approve.
Create the follow-up from a meeting
An action item becomes a ticket draft, with the owner and the link to the call.
Rank what slipped
The morning report cites the issues that moved, stalled, or lost an owner.
Keep other boards out
A board becomes a project. Other boards stay out until you invite Morrow in.
Tie the ticket to the page and the thread
The issue, the Notion spec, and the Slack decision share one record.
How you connect
Connect once. The brain starts from there.
- 01
Connect the account
One click into Jira, where the tool allows it. Morrow inherits that person's access — nothing wider.
- 02
Work writes itself in
The Jira records you scope to the project land in the company brain.
- 03
Agents act after you approve
Mor drafts the Jira update. Nothing is written back until you confirm.
In practice
What teams ask for
Standup that already knows the board
The draft lists what slipped and who unblocks it, from Jira rather than a round-robin.
Ticket opened from the call
A meeting action becomes a proposed issue. You approve before it is created.
Comment that cites the spec
When scope moves, the agent drafts a Jira comment that points at the Notion page.
Before you connect
Questions about this connection
Does Mor see every Jira project?
No. Only the boards you invite into a Morrow project.
Can agents transition issues?
They can draft the transition. It is applied after approval.
What if we disconnect Jira?
New issues stop syncing. Captured memory stays until you delete it.
Often used with
