Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Set the previous value before the script listener trigger



I would like to make a script listener with trigger- issue updated.

Inside the code I put a condition- if it's true I want that the update that made didn't save, and the previous value will keep.



fixVersions = x

update issue - fixVersions = Y

if condition = true

fixVersions = x

1 answer

0 votes
Tarun Sapra Community Leader Jul 24, 2018

Hello @Dan27

You can easily achieve this by using the "ChangeHistoryManager" to fetch the values for a specific field in the script listener, for example for Fix Versions something like this should do the trick

List<ChangeItemBean> changeList = changeHistoryManager.getChangeItemsForField(issue, "Fix Version")

 And then use the changeList to fetch the ChangeItemBean.

But as you said in your description

 if it's true I want that the update that made didn't save, and the previous value will keep.

This is not possible is Jira to "not" save the value because listener is fired after event has happened so the fixVersion will become value Y in DB but your listener script can change the value back to old value X thus to the end-user it will appear that the value has never changed but actually your listener overrides the new values with the last value.

Thank you @Tarun Sapra ,

Is there an import I need to add?

You need to add this

ChangeHistoryManager changeHistoryManager = ComponentAccessor.getChangeHistoryManager();

And these imports

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.MutableIssue
import com.atlassian.jira.issue.changehistory.ChangeHistoryManager
import com.atlassian.jira.issue.history.ChangeItemBean 

@Tarun Sapra amazing thank you!!!!

But now I can't put this version in the 'FixVersions' custom Field of the issue


Tarun Sapra Community Leader Jul 24, 2018


Hello @Dan27

Issue.setFixVersion expects an list but you are passing a single string which is not correct, thus you see the error, please go through the APIs here

Hi @Tarun Sapra , 

this code: 

List<ChangeItemBean> changeList = changeHistoryManager.getChangeItemsForField(issue, "Fix Version")

Gives me a string... how can I edit the fix versions with this value?

Hello @Dan27

It returns lists of ChangeItemBean which you need to parse to get the string value which you want

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

168 views 6 7
Read article

Community Events

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

Events near you