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.
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs