Creating more than 1 tasks in Jira Automation is causing fields to be reverted

[Garrett McCreery]

This issue has only started happening as of 9/28/2021...

1. Create an automation
2. Add create issue step
3. Set values for fields
4. add another create issue step
5. Set value for fields
6. Click off of second create issue step
7. Click back into second create issue step
8. See that field Due date is changing to Due date from first create issue step

Pics won't work for this, so here is a link to a video:

https://youtu.be/YRmbTjhl0zc

[Jack Brickey · Accepted solution]

I wonder if it is actually changing the due date on the first create issues step or if rather your change is not saving. My point is in your video you had now in the second step and then you edited and replaced it. And when you returned it went back to now. It appears that you did click save. On the surface it sure seems like a bug particularly if it is just started happening to you. I would refer you to that Lassie and support so they can login and have a look. It would also be interesting to see if you could change that due date to something else such as a specific date just as a test.

[Garrett McCreery]

Yes, saving as well... Seems to be only the due date field... Here is the support ticket: PCS-59249

[Bill Sheboy]

Okay, I have reproduced the symptom and it seems like a screen refresh issue in the rule editor.

I found that after your step 7, I do see old values staying on the page.  If I click up on the trigger (or another non-create-issue action), and then go back to the problematic component, the values are correct.

Of note: I often see "oddities" in the rule editor and list view.  One of my test projects has dozens of rules and often hangs while painting, requiring a pause/refresh to load.  Updates in that case seem related to the usage of many labels.

[Garrett McCreery]

well I guess that is a workaround for me while they get this fixed. Thanks @Bill Sheboy 

[Jack Brickey]

good find @Garrett McCreery 

[Garrett McCreery]

Guessing there was a recent release that broke this because I write automation almost every day. Thanks @Jack Brickey 

[Garrett McCreery]

Ticket opened by Atlassian.. see https://jira.atlassian.com/browse/JRACLOUD-77467

[Bill Sheboy]

Wow!  Watching that video in the ticket, it seems there is also a data/state-management problem as even though it was the view not refreshing, selecting "save" does overwrite the other action's values.  This has the potential to mess up rules if someone is doing edits.  And if create issue is "bent", what else may be broken similarly in the editor?

Thanks for finding this one, Garrett!

[Jack Brickey]

so bizarre. not sure I would have made the bug Low priority. I get that there is a work around but not a pretty one. :-(

[Garrett McCreery]

FYI.... for any future readers, this issue was resolved. see https://jira.atlassian.com/browse/JRACLOUD-77467

[Bill Sheboy]

Hi @Garrett McCreery 

Are you selecting to save your changes before moving to another component?  I cannot tell from the video.

If you are...I do not see any open incidents on the status page for automation so you may want to quickly submit a ticket to support so they can check your logs: https://support.atlassian.com/contact/#/

Kind regards,
Bill

[Garrett McCreery]

Had other users test this as well. Happening for them also as of late yesterday (9/28/21). Have you tried it to see if it's happening to you?