I have a few postfunctions that I've added that are changing some fields after the system step "Update change history for an issue and store the issue in the database."
I have a Clone step after the issue was updated with a few fields specified in the transition screen. What I want is to make some additional changes to the issue before it gets cloned but I don't want these changes to persist on the original issue. For now, this is working perfectly: the changes are made and it's reflected in the cloned issue as intended. The changes don't appear in the change history of the original issue nor are they saved on the original issue in any way.
Is there some residue / risk involved with this method? I'm quite happy with how it's working out so far.
In case this is not clear (it probably isn't), my postfunction list looks like this:
Customfield_x is properly set for the cloned issue but is missing from the original issue (intended). What I'm asking is if there's any chance of this biting me if I use it long term. Is there any chance of customfield_x changing value on the next transition? Or are all changes after step 3 discarded completely after the event is fired?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Atlas Camp is our developer event which will take place in Barcelona, Spain from the 6th -7th of September . This is a great opportunity to meet other developers and get n...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs