Trying to find why my rule doesnt work

Natalia Mojica
Contributor
October 4, 2023

Hi, I'm trying to create a rule (in the automation section) to add a comment when an issue is created and it has a specific status (Needs more info):

Captura de pantalla 2023-10-04 a la(s) 10.01.02 a. m..png

  • The problem is when I create a problem and assign it as status 'Ready for design' I get the notification message (for the automation rule), but this message should only be there when the ticket has a status of 'needs more info'
  • I added the condition Status is not equal to 'Ready for design' because only with the status condition equal to 'Needs more info' the rule didn't work. But with this other condition the rule didn't work either.

I don't know if it's useful, but the workflow of my states in my project is this:

Captura de pantalla 2023-10-04 a la(s) 10.31.30 a. m..png

 

2 answers

2 accepted

3 votes
Answer accepted
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 4, 2023

@Natalia Mojica -

To supplement what @Mikael Sandberg stated, you should also look into your automation rule so that the triggering event is chosen properly.

If you want to add comments when issue is created, then "issue created" event is correct.  However, you cannot/should not test for the status condition because when issue is created it will always be assigned to the initial status as defined in the WF.

If you want to add comments when an issue is at a specific status, then the triggering event should be "Issue transitioned" or "Field value changed". This is where you can check on the status condition.

Hope this also helps.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

1 vote
Answer accepted
Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 4, 2023

Is problem its own issue type? 

There is a couple of things you could try, one is to simplify your automation since Needs more Info is the first status newly created issues get based on the workflow. So if everything works all you would need is the issue type equal story condition. Another would be to use the JQL condition instead and see if that helps, your JQL would look something like this:

issuetype = Story AND status = "Need more info"

Suggest an answer

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

Atlassian Community Events