JIRA AUTOMATION - JQL condition

[Mane Zakaryan]

Hello,

Can anyone explain what is wrong with my condition and why it is not working.

1. I have a Story created automatically (it is my second issue in the order)

2. My JQL condition suppose to check the Status of my Story and if it is CLOSED it supposed to create a new Story (Story release) with its sub tasks. My Story is not creating.

Thank you in advance for any help.

[Bill Sheboy · Accepted solution]

Hi @Mane Zakaryan 

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Until we see those...

The JQL condition needs valid JQL, and thus you can check an issue field to a value, with operators:

• someField someOperator someValue
• such as with issueType = Story

But you are trying to check a smart value, {{createdIssues.get(1).status.name}} on the left side, and that cannot work.

Please instead try an Advanced Compare Condition rather than the JQL condition.

Kind regards,
Bill

[Mane Zakaryan]

Hi @Bill Sheboy 

Thank you for your feedback.

So I will try to capture my complete rule. It is a little bit long but I will try to be clear.

First step

So I have a trigger issue, and when my Trigger issue change its status so I have a creation of my Epic. This step is working correctly.

Second step

At the same time I have a creation of my first story with 3 sub-tasks. This story is created in my Epic of the first step. At the same time I have a comment which is adding from my trigger issue. This step is working correctly.

Third step

At the same time, I have a creation of an separate Task which is linked to my Epic. This step is working correctly.

Fourth step

At the same time I have another Story created with its 9 sub-tasks. This story is created in another Epic which is not related to my rule but at the same time it is linked to my Epic of First step. This step is working correctly.

Fifth step

So after all this 4 steps, the developers will work on their tasks. But for my Story in Second Step, when the developer will put all his tasks in ''Done by Devloper'' and Team lead will put them in ''Closed'' after the check, in this moment I need to have a Story for Release with sub tasks that are necessary to do fro pushing on prod my project. 

1. First I want to check the Status of my story in Second Step. This is not working
2. Then If my Status is CLOSED at this moment I want the creation of my release story with its sub tasks. This is not working. This is not working
3. I want that my release story were created in my Epic of the First step. I think it is correctly working, just I need my Story created first :) 

[Bill Sheboy]

Are the steps you note separate rules, or all one rule?  If they are in one rule, it can help to show these in one image for context.  That can be done using a screen capture tool or browser addon for scrolling, page capture.

For your Fifth Step, it seems that should be a separate rule, as it has a different condition than the earlier steps.

When a simple condition is used, if the condition is not met, processing will stop.  If all of your steps are in one rule, then the Fifth Step will never be reached.

An alternative to the simple condition is to use an if/else structure.  For example:

• trigger: issue transitioned
• if/else condition
  • condition: some test
  • action: some action
• else/if
  • condition: some other test
  • action: some other action
• else
  • action: another action
• ...continue processing steps...

Next, and again without seeing your entire rule, I wonder if the conditions and branching are creating problems:

• Inside of a condition (or branch) issues can be created.  However outside of that branch, the "most recently created issue(s)" is not always visible.  This depends upon the rule structure.  And when this happens, things like your branches on most-recently-created-issue will not work.

Please review these ideas for any adjustments.  And if you can post a single image of your rule that may help clarify what is happening also.

[Mane Zakaryan]

Everything is in one rule.

Here is the complete capture.

[Mane Zakaryan]

You are right, it will be easier to create a new rule and if I don't find solution, I will make so the release story is also craeted with others at the same time and I will manage manually when the Dev should work on it.

But I will think on your if/else rule creation solution, maybe I will succeed,

Thank you for your support.

[Bill Sheboy]

Thank you, and that confirms the cause is using conditions and not if/else conditions AND that the most-recently-created issue from earlier is not visible later.

Please consider how this rule may be either split up, or use if/else structures so the processing does not stop.

[Mane Zakaryan]

Very well, I will keep in mind and I will continue. 

Thank you very much.