unable to set a field - true of false using behaviour plugin based on a field value change during bulk edit

saravanan subramanian October 24, 2016

Hi All,

I have a single choice select field, when ever there is a change in value and the selected value is not equal to the original value, i will set another text field to true using a behaviour script. It works fine during single edit but not during the bulk edits.  Is it possible to exhibit the same using the bulk edits.

 

Please let us know

2 answers

1 vote
MikeyS
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 24, 2016

Behaviours works on the Create, Edit, and Transition screens in JIRA, but only in those contexts. It won't work with changes done through bulk edits, post-functions, or the REST API.  It's very javascript-y.

It sounds like you will want to write either a scripted field or a listener (both available with ScriptRunner). The scripted field is probably the more elegant solution, so that's the one I'll describe.

The scripted field could replace your text field, and you could set its value based on the change history of the select list field. You would write your scripted field to find the original value of your select list field using the ChangeHistoryManager. You can then compare the original value of the select list to the current value, and set the value of your scripted field based on the outcome. This way you don't need to worry about detecting changes.

saravanan subramanian October 25, 2016

Thanks for your help. Do you have any documentation of this solution!

MikeyS
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 25, 2016

No, sorry. I would just search for other ScriptRunner scripts that use the ChangeHistoryManager. Also, I'd do some testing in the Script Console first to see what I was working with. Just grab an arbitrary issue with the IssueManager and then use the ChangeHistoryManager to getAllChangeItems() for that issue. If you leave that variable as the last item in the script, the Script Console will print it to screen when you run and give you a good idea of what you're working with.

saravanan subramanian October 25, 2016

Thanks Schott. Based on the document i read , the scripted fields are read only is that correct?

0 votes
saravanan subramanian October 26, 2016

Thanks for your help Schott. I got it working using change-history manger . The only issue with that it is a read only field which i cannot change , so i have to add an additional field to do the manipulation.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events