Hello,
I've been using JIRA issue templates for a few weeks and have developed some epic templates for our group.
One of the epic templates has around 10 tasks attached to it as children. It has required significant effort from teams to build the entire structure.
I'm concerned that someone could accidentally delete or modify the template.
Is there a way to export it and all the tasks attached to it? I can see how to export the epic template as a word document and xml, but it only exports the epic and not all the tasks.
Also, once it's exported, how can I import it?
Hi @Will Ferry
It's Aleksandra from Deviniti, the vendor of the Issue Templates for Jira app.
After reading your post, I suppose that the challenge you faced may relate to templates created with the help of our app, therefore I'd like to share further guidance.
To start with, I would like to explain that in order to control access to editing templates, you could use native project permissions and restrict who can edit issues (namely templates) in your repository project by assigning a specific project role (e.g. project admin) to Edit issue permission. In this case, every template is just like a regular Jira ticket, therefore it will be subject to all issue permissions.
If it comes to exporting, I believe it would be best to export template issues to a CSV file directly from Issue navigator as explained in this article in Atlassian documentation.
This way, you could easily import them back if needed:
To narrow down the results and export only the Epic with its Stories, you could use such an exemplary query:
project = REPO AND (issuekey = {epic_issuekey} OR "Epic Link" = {epic_issuekey})
I hope that you will find my instructions useful. In case of any additional questions, feel free to contact me!
Best,
Aleksandra
Hi Aleksandra. Thanks for the answer.
Let me check that out and get back to you.
Appreciate the help!
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.