Hi everyone,
I need to change the value of a custom field when an issue is moved from one project to another or from one parent to another. For this, I plan to use a scriptrunner listener ( cloud version). However, the only listener that can relate to this is the issue updated one. How can I be sure that the script is triggered only for a move process and not for any other update? And how can I be sure to access the detail of the updated issue and not its previous properties?
Thanks,
Cédric
Hi @Cédric Cox
What about if you still use the Issue Created event and in your code look for the history by expanding the changelog.
/rest/api/3/issue/ESD-20?expand=changelog
If the issue is created by moving then it will have this entry.
{
"field": "Key",
"fieldtype": "jira",
"from": null,
"fromString": "ISD-17",
"to": null,
"toString": "ESD-20"
}
I hope it helps.
Ravi
Thanks Ravi. But I finaly tried Jira automation to perform this.
However, this is not working:
I try to copy the parent key into a custom field. The action results in a success according to the audit log, but the field remains empty. That's puzzling.
Any help with this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No. I will if I find no other solution. I already use scriptrunner for other things and I wouldn't like to install another addon.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.