i have multiple scrum teams.
some teams have per team specific repeating issues (stories) that they execute each sprint as a new instance - e.g. run the weekly report.
they want to create different templates available to their team to select from when creating a new story.
is this possible?
they have been using a dummy boiler plate actual story and cloning it, but those stories while sitting at the bottom of their backlog, are annoying to see as a long list of "CLONE THIS" prefixed stories. ideally the solution would be a drop down list of story templates e.g. "story template for weekly reports" "story template for monthly reports" with the relevant Acceptance Criteria, DOD, tasks, overview "as a i need so that" and points already assigned as defaults
Hi @Kathryn Lee ,
Yes, this is possible. Jira’s native Forms or scheduled Automation can cover some simpler cases, particularly when the story should be created automatically every week or month.
For the template-selection experience you described, a Marketplace app would provide a closer fit. I’m from the team behind Easy Issue Templates for Jira, which allows you to:
The templates are stored separately from regular Jira work items, so you would no longer need the “CLONE THIS” stories sitting in the backlog.
For enterprise environments, the Cloud app is also Runs on Atlassian and Cloud Fortified, with SOC 2 coverage and participation in Atlassian’s Marketplace Bug Bounty program.
For genuinely scheduled work, you can also connect a template with Jira Automation so that the complete story is created automatically each week or month.
Feel free to reach out if you have any questions.
Best,
Paul
Yes, this is absolutely possible in Jira Software Cloud using the native Forms feature. While forms were previously exclusive to Jira Service Management, they have now been rolled out to all Jira Software projects.
The Forms tab in your Jira Software project navigation is the perfect tool for this. It allows you to create structured entry points for new work items without needing "boiler plate" issues sitting in your backlog.
Benefit: When a team member uses the link, they see a clean form with all the defaults ready to go. Once they hit submit, the story is created directly in the backlog, and you no longer need those "CLONE THIS" issues taking up space.
Automation Flows: For truly "repeating" issues (like a report that happens every Friday), you can use Automation (Project Settings > Automation) to create the issue automatically on a schedule.
Marketplace Apps: For even more advanced needs (like templating an entire hierarchy of an Epic with 10 Stories), apps like Issue Templates for Jira are available.
If you'd like to see a more integrated "Template" dropdown directly inside the global "Create" button, you can vote for and watch these active suggestions on our public tracker:
https://jira.atlassian.com/browse/JRACLOUD-7731: Request for native Issue Templates to handle recurring tasks.
https://jira.atlassian.com/browse/JRACLOUD-63186: Suggestion to allow users to define "Template" issues for quick creation.
Verified Documentation:
I hope this helps your teams stay organized and keeps your backlog clean!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.