Automation rule not working when "Story Points" value change is trigger for status update

Andrei Iftimie November 10, 2023

Hello Jira community, I am trying to create a very simple rule which should allow automated status transition from "TO DO" to "Ready for development" whenever the field "Story Points"  changes to any value. BY default the value is null (nothing pre-filled). For some reason the rule is not even triggered although no syntax issues were detected.

Can you please advise what may be the issue and whether any work-around is available?

Thank you

jira automation rule fails - Story Points field value change.png

jira fields from project and explanation.png

2 answers

1 accepted

4 votes
Answer accepted
Chris K
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 10, 2023

Hello @Andrei Iftimie

You configured the trigger for the operation “Transition issue”. That means the rule only will trigger, when the issue is transitioned to another status. Try the rule again after adding the "Edit issue" operation.

Hope that solves the case :)

Greetings Chris

Andrei Iftimie November 10, 2023

Offf course, got bitten by the exclusive focus on transitioning the status and misinterpreted that field. Feel bad about it now :) by how simple it should have been. Thanks for opening my eyes on this, that indeed solved the issue and was an obvious thing to do if I look retroactively. Cheers!

Like # people like this
Chris K
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 10, 2023

I feel you. But don't worry, that happens to all of us, like me yesterday on a similar topic :D

I was sitting in front of a non-working automation for hours after realizing it's only a small change which makes the damn thing working. That was embarrassing, but also relieving at the same time. Focusing on the relieving part, makes life much easier :D 

Greetings

Chris

Like # people like this
0 votes
Murat Seven
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 10, 2023

Hi @Andrei Iftimie and thanks for your question.

 

I have created an automation for testing, and I am receiving success.

Could you please provide screenshots of the issue where you changed the "story point" and the "rule details" sections of the automation?

Andrei Iftimie November 10, 2023

Thanks a lot for the swift reply. Please see nearby the details and also note that even when the actor is "jira automation" tech user, it still doesn't work:

Rule details section.pngdetails of automation rule using SP as trigger.pngevidence that automation rule did not work.pngevidence of Story points value changed.png

Murat Seven
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 10, 2023

@Andrei Iftimie  and Thank you for response.

 

Could you please clarify whether you are setting the "story point" field within the transition screen in the "field value changed" section where you have selected "transition issue"? If I understood correctly, you are updating the "story point" field in the "edit issue". The issue seems to stem from this. If you remove the value for "transition issue" in the "For" section, the problem should be resolved.

Like Deleted user likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events