Jira Automatoin Rules not Updated after Editing

[Linda Milne_Togetha Group_]

I have some jira automation rules that are working but I need to make a few changes to them, for example change the Summary of a sub-task that is being created.

I can type the change needed but moving out of the Summary field (in a number of different ways) doesnt save the changes and the value reverts back to the original value. I can sort of get bits to work but I cant see whats is going on.

I can over-write part of the Summary text for the creation of a new sub-task, but not another part of the text. I am trying to update the text:

ID02 xxxxxxxx - {{issue.customfield_22222}}

I can edit the ID text, but not the xxxxxx section - this is the bit I actually want to change. The smart values caused no end of trouble when the rules were originally created, with not saving properly. For the updates, I have found that if I add the new text:

ID02 yyyyyyy xxxxxxxx - {{issue.customfield_22222}}

tab out of the field, go to another step, then come back and delete the text I dont want I can get it to update. This works but its horribly long winded.

I also have an if-then-else that I want to add some new conditions to and I cant find any way to add or update these values. It looks like I have to completely re-create the rule if I want to make these kinds of changes.

I cant find anything on problems with using smart values or editing rules. Does anyone have any suggestions.

[Bill Sheboy · Accepted solution]

Hi @Linda Milne_Togetha Group_ 

There is definitely a learning curve for the new rule editor UX, and I have noted some glitches / changes in behavior in the last few days...

To make a change to an action, one usually must select the Next at the bottom of the action for the changes to persist.

And to add to existing structures, such as an if / else, the rule must be in a stable state first.  (For example, you can no longer copy an existing rule component when a rule is in an unsaved state.  Instead either the new component must be added from the selections at the top-right or the rule must be updated / published first.)

When adding to an if / else with the new UX, it can be tricky to confirm the correct location is selected for adding an additional clause versus to the else block.  Fortunately adding a component, and then dragging it elsewhere, still seems to work predictably.

I recommend trying the above first to learn if it helps.  If not and you have reproducible steps for problems, please contact the support team so they can help: https://support.atlassian.com/contact/#/

Kind regards,
Bill

[Linda Milne_Togetha Group_]

Thanks @Bill Sheboy 

The Next button doesnt seem to always work, but yes, it does seem to work "most of the time". Updating the rule after each change (before leaving the field being edited) seems to be the best option.

For adding to the if-then-else I am making the changes to a saved rule, not having made any other changes. I wasnt able to drag and drop the if-then blocks - I can drag and drop the then block, but I cant move the entire block. So re-ordering, without lots of re-writing conditions, is not an option as far as I can tell. Is there something in particular that Im supposed to do to make this work?

I did find a way to create the a new if-then block in the middle of a set of if-then-else blocks - hover over the space just above the else-if label and the option to add a new block shows up (not seen that before). I did want to add a new block at the beginning of the if-then else, which doesnt work, but I can add a new if-then block at the first else and edit the contents of each block to give me required condition order.

[Bill Sheboy]

Thanks for describing those symptoms further!

For the inconsistent problem with saving and the Next button, perhaps enter feedback (after selecting the Update button to publish a rule) or contact Atlassian Support if you can reproduce the symptom.

Regarding drag-and-drop for if conditions...I was noting dragging the other components, not the entire if block.  In the old editor, it was intermittently possible to drag entire if and branch blocks...allowing structures not by-design for rules, and which rarely worked as expected.  That appears to be "fixed" now.

[Linda Milne_Togetha Group_]

An update on this. I have continued to have this problem - updates to the Summary field in automations when creating an issue would sometimes work and at other times not. It seems that the problem is cut and paste. I have had 100% success when I have typed the summary field value that I want. Go figure.

[Bill Sheboy]

Thanks for the follow-up, Linda.  Did you contact the Atlassian Support team to learn what they think about this symptom?

[Alan Stephenson]

What version of jira are you using? Latest LTS? Able to share you rule?