nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation for Jira workflow transition not updating-ish. Jira problem or Automation problem?

Todd Palermo

I have created an Automation for Jira (3.9.4) rule to transition an issue when a field value changes that matches a JQL condition. This rule works behind the scenes, but the status does not update visually in the issue unless I refresh the issue or page. I have tried adding a Refresh issue Action at the end of my rule, but that still doesn't correct this problem. I am running a trial on Automation for Jira right now and I would really like to know how to fix this before I spend any money. I am using this on Jira Core Server 7.6.2. So, is this a Jira or Automation problem?

Accepted answers

Danyal Iqbal

Are the transitions for the next status visible?

Is the Transition visible in the transitions tab?

Is the field value changing as a result of a transition? and you basically want to make 2 transitions with 1 action? Automation for Jira (3.9.4) is not the right tool for this. This should be a webservice not a listener.

All comments

Danyal Iqbal

Are the transitions for the next status visible?

Is the Transition visible in the transitions tab?

Todd Palermo

Yes, the transition is visible on the transition tab. Jira knows whats up because when I try to manually transition, I get an error that says the task has already been done and I need to refresh the page. I was expecting Automation to change the Status from Not Ranked to In Progress, but it doesn't do it on its own. I am not sure about your comment about the right tool, it seems that the rule looks exactly like I would expect, but I am not in the software industry... I am in the business sector... so I do not know what you mean by a webservice and listener. Are you saying that the rule below will not work?

Danyal Iqbal

You cannot perform 2 transitions with 1 action. If the value of Problem Rank is changing as a result of a transition than this rules will not work.

Have you tried changing the Problem Rank using the edit dialog on the issue screen?

Todd Palermo

I think I am doing it as you suggest.

I may not have explained the scenario correctly. A problem is created and is in the first status "Not Ranked". When the user edits the problem field "Problem Rank", then this rule sees that the value has changed from empty to not empty. Then the transition is changed to Start Progress. This happens, but the screen doesn't display "In Progress", however, Jira knows that it is "In Progress" because when I try to manually change status with the transition button, I get an error telling me that I can't move to "In Progress" because I am already "In Progress". I may need tech support from the developers. This seems to be a bug on their end.

unknown

Did you resolve the issue? If I refresh the screen twice the status gets updated, but not before I do it twice.

Jakub Bobran

+1 for this issue.

I've also created rule for moving subtasks along with their parent.

Status of subtasks transition corectly. The only issue is that it won't update/refresh Board view. It has to be done manually (single F5/Refresh).

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

addon-com.codebarrel.addons.automation

transition

board

hierarchy

automation

sub-task

refresh