DO NOT CHANGE A JIRA DATABASE WHILE IT IS RUNNING
Apologies for the shouting, but you need to understand that. If you amend Jira issue data with SQL, you *must* have stopped Jira before running the SQL, you *must* have taken a database backup and proved you can restore it ok, and you *must* reindex Jira afterwards. Or things break.
There's no way to change the link via REST, you will have to use the API to do it - either use the GUI or write something to expose the link values over REST.
Nic is right.. Database change is the last thing you want to do. But wait.. Why you cannot convert a subtask to and issue and then convert an issue to a sub-task back again?
This will allow you to change the parent to other ticket without touching the database or using REST.
Other case if you want to do it for mulitple issue.. Since this option is only available for single issues.
Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot