Back to catalog / Agent workflows
Turn planning notes into Jira work items
Break iteration-planning notes into assignable Jira issues with acceptance text, then create them in the project.
Goal
Convert high-level planning items into a trackable Jira backlog rather than a meeting summary.
Steps
- Provide approved planning notes and the target Jira project/key. [src10-strands-turn-planning-notes-into-jira-backlog]
- Have the assistant turn each plan item into a concrete task with scope, acceptance points, and necessary context. [src10-strands-turn-planning-notes-into-jira-backlog]
- Review the list, then call create_jira_ticket for each item and save the returned issue key. [src10-strands-turn-planning-notes-into-jira-backlog]
How to verify
In Jira, check the new issue count, summaries, and descriptions under the project; sample-check that each has verifiable acceptance criteria.
Troubleshooting
Before creating duplicates, search existing issues by the plan heading; for oversized tasks, add the meeting decision and split boundary before retrying that item.
Permissions
Prerequisites
- A Jira project access token, target project/key, and reviewed planning notes.
Permissions
- create_jira_ticket creates issues in the selected project; confirm scope, titles, and visibility before submission.
Limitations
The sample is a single Jira assistant; it does not automatically assign owners or estimate story points.
Pinned upstream source
- Repository
- strands-agents/samples
- File path
- python/04-industry-use-cases/productivity/scrum-master-assistant/README.md
- Pinned commit
bd46f959844424a9544133e1263c8eae61e7fe9b- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: Apache-2.0
Main topic
Turn ecommerce campaign materials into a reviewable weekly brief