Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation rules are not updating without refresh

Jeroen Kolk October 20, 2023

Hi all,

I saw this subject multiple time passing by but that was a while ago.

Underneath the explanation of my issue:

I have three automation rules.

 

  1. First rule: 
    When the user moves a subtask from 'To Do' to 'In Progress' the status of the story will be updated to 'In Progress'

  2. Second rule:
    When the user moves a subtask from 'To Do' to 'In Progress' the user who did the action will be assigned automatically to the subtask

  3. Third rule:
    Whe the user moves a subtask from 'In progress', 'in review' or 'done' back to 'To Do' the subtask will be automaticall unassigned.

 

I started with rule 1 and when activating the rule it only updated after a refresh.
Rule 2 and 3 will update after two or three seconds.

In all the rules underneath the 'more' option I selected 'Trigger rule directly' 


You can see the rules in the screenshots.

I hope anybody can help out to apply the first automation rule immediately without refreshing the page.

Screenshot 2023-10-20 at 11.51.10.pngScreenshot 2023-10-20 at 11.51.26.pngScreenshot 2023-10-20 at 11.51.40.png

1 answer

0 votes
Tom Lister
Community Champion
October 20, 2023

Hi @Jeroen Kolk 

I'm not understanding why you have applied the first rule. The workflow transition built in actions should change the status to In Progress.

The rules will be active as soon as they are published but won't be run until a trigger action is detected.

If rules are updating issue field it can take a while for that to be reflected on the issue view.

When rules may have dependencies ensure they are allowed to be triggered by other rule actions

Screenshot 2023-10-20 at 11.11.02.png

Jeroen Kolk October 20, 2023

Hi Tom,

Thank you for your reply.
I am not sure I understand you.

Do you mean with the first rule, JIRA should already do this out of the box?

All the rules are published and are also set to active. They all work but only the first action needs always a refresh. 

 

Kind regards,

Jeroen Kolk

Tom Lister
Community Champion
October 20, 2023

Hi @Jeroen Kolk 

If you transition an issue the status will be updated out of the box.

Screenshot 2023-10-20 at 13.35.34.png

Screenshot 2023-10-20 at 13.37.17.png

I have just checked you rule again. Are you intending to transition all sub-tasks to in progress? ( I have no Dutch :-) )

Is so the issue may be that the data displayed in the issue view won't be updated to reflect changes in linked issues. The event chain to make that happen would be too complex.

You can emulate the same behaviour but editing the sub-task in another tab. The issue view in the original tab won't be updated.

But if you hover over the sub-task in the original window, the pop-up view will show your changed status.

Screenshot 2023-10-20 at 13.45.09.png

I am not aware of any options to get around this.

Jeroen Kolk October 20, 2023

Sorry, at my work they set the language to Dutch and I cannot change it.. :(


I am intending that when I move one subtask from TODO to IN PROGRESS, that the status of the story where the subtask is in will be automatically set to INPROGRESS.

I use branche function to be able to get to the parent of the subtask to change the status. I read somewhere that this could give an issue with updating directly.

But I have the feeling it has to be possible since this is such a mandatory automation you would like to have within a JIRA board.

Tom Lister
Community Champion
October 20, 2023

Hi  - I think it is the same issue, that the issue view does not immediately display any changes to the underlying data on the screen.

If you have the parent open in two tabs and change the status in one tab it will not be reflected in the other until you refresh or perform some action that causes a refresh.

This can look odd if you try to transition an issue as the displayed status may not match the available actions until you refresh

Are you updating the parent issue or transitioning the parent issue. That latter would make more sense to me.

I assume your automation updates are working but Jira is not displaying in a user friendly way. I think the assumption by Atlassian is that users are moving through issues quickly and update events don't need handling in the display.

Suggest an answer

Log in or Sign up to answer