Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Create ChangeHistory Group/Item Entry with Scriptrunner


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.

The Problem

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

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events