How can I manage repetitive stories in Jira? Templates are a blocker

[Vlad]

I'll try to describe the use case as simply as possible

• I'm working with a team building multiple APIs and backend services.
• We enforce agile practices in the team, so we write agile stories in Jira.
• For all the new apps we build, there's a set of common stories that need to be added to the backlog for that app.

Based on the points above, my question is:

What's an effective way to keep a list of repetitious stories in Jira so we don't have to search/copy/paste them every time we need the story in a new project?

I tried using templates but was told I need SuperAdmin privileges to create templates. Seriously?? 

[John Funk · Accepted solution]

Hi Vlad - Welcome to the Atlassian Community!

You might try creating some standard Stories with the information you want. Then simply clone the story when you are ready to create a new one. 

[Vlad]

@John Funk maybe I'm missing something, but is there a place in Jira (other than the Backlog) where I can keep those generic stories to reuse them later?

Thanks

[John Funk]

You could add another status to your workflow and park them there. 

[Vlad]

Hi John,

By "workflow", are you referring to my list of generic stories?

By "park them there", are you referring to keeping the list of generic stories in the Backlog?

Thanks

[John Funk]

No, by workflow, I mean the statuses or steps in your workflow. Add a new status from Backlog called Template or something like that. Create the issue and getting it the way you want it and move it to the Template status (or whatever you call it. 

Then you can simply clone it when ready for a similar issue. 

[Vlad]

Not what I was expecting from Jira, but since there are no other suggestions, I'll try this path and see how it goes. 

[Julien Peyrade _ Elements]

Hello @Vlad Carballo 

I think this use case is what you are trying to achieve?

Leverage a template project in Jira by bulk copying issues.

If yes, I hope that you find the attached tutorial helpful.

Kind regards,

Julien

[Vlad]

Hi Julien, 
Thank you for the reference, but I'm avoiding adding another tool to solve a simple requirement that Jira should address.