We have the following use case
There is a scripted listener which checks newly created comments. If the comment contains a keyword, the current issue needs to be closed, cloned, and the cloned issue needs to be moved.
Due to audit and security reasons creating a clone directly within the destination project is not an option - using a workflow post function neither due to multiple combinations of keywords and destination projects.
While moving an issue is not part of the public Java API for Jira, I would like to create the clone of the issue into the destination project and "simulate" the move by only adding an entry (ChangeHistoryGroup with one ChangeHistoryItem) into the ChangeHistory of the newly created issue.
This solution would look like the issue was moved while it basically was cloned only.
While accessing the Issue history is very easy, I was not able to find any option how to add new entries manually, without actual changing/updating the issue. And as updating the project is not possible, the regular issue update will not work here.
As the SQL structure of the change history is very well documented by Atlassian, running SQL queries would be an option also, but changing the sequence counters manually this might be too risky for a daily action while the system is running.
Does any someone have an idea how to implement this with Scriptrunner?
Best regards and thanks in advance
Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events