You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I am trying to bulk upload issues and I want an Issue Template applied to the issues. I keep getting an error. It does pass validation, but it errors on upload. The error is like the error shown in this JRASERVER-64670
Nevertheless, Is this something that can even be done? Is there anyway to create many Jira Tasks using an Issue Template without having to create each task manually one at a time?
Here is the csv upload showing the Issue Templates field. If I remove this field, the upload works.
That's because all the other custom fields are 'inert'; they are just containers for holding data. That custom field Issue Templates belongs to the Issue Templates for Jira app and is 'active'; changing it triggers actions on the backend by the app, or it has some other attribute that doesn't allow it to be changed in the manner you're trying.
Issue Templates for Jira SERVER does have a REST API that is integrated with Jira's, and it supports what you are trying to do, so you can use that method to upload all the issues into Jira and set that custom field's value which in turn would trigger the app to make each issue be based on a template. If your company has developers, you could employ them to create a tool / script to parse your CSV file and upload the data to Jira's REST API and solve the problem that way.
Lastly, the Create issue from a template section of the REST API docs says that custom field is set to a numerical value, which represents the ID of the template. As an experiment, try uploading the CSV file again and give the Issue Templates field a numerical value, not the text name of the template, and see what happens.