Automation to create new card

[Brandy Richbourg]

Using Jira Scrum board...

This is what I need:

• when a story is created and YES has been selected in a specific field (called push to prod)
• when that story is moved to DONE
• a new story is automatically created and assigned to specific user prompting the push to prod

I can't seem to get it right in the automation. Anyone know the steps?

[Brandy Richbourg]

Issue transitioned > issue fields condition > push to production = Yes > then: create a new issue type (same issue type) > assignee DV

When I tested it and ran the audit log the status says NO ACTIONS PERFORMED and action details: Issue condition the following issues did not match the condition: MS-2041

[Jack Brickey]

Hi @Brandy Richbourg , welcome to the Community.

Here is the basic structure I think. However, understand that you can't prompt the user in real time as the issues being created within automation. What you can do is send an email to that user requesting that they complete the field.

Trigger - Issue Transitioned to Done

Condition - Field condition > push to prod > equals > YES

Action - Create issue, set Assignee, add comment "Please do xxxxx"

[Jack Brickey]

Feel free to share your current automation and I can inspect and provide more input.

[Jack Brickey]

Hi Brandy, please use the reply box rather than the suggest an answer box so that it keeps the discussion within a single thread. This will make it easier for us and others to read in the future.

If you would please send a screenshot your automation that would be best. One other thing I find useful when creating rules is to use the "Log Action" to record data when the rule is triggered. For example you could use the log action and record the value in the"Push to production" field. Of course in this case you know the issue ID so you could always just inspected after the rule.

[Brandy Richbourg]

[Brandy Richbourg]

Where is the log action? Sorry, I clearly have no idea what I'm doing.

[Jack Brickey]

No worries Brandy! It is all about learning new things.

The Log action is an Action you can add in your rule. Similar to the Creat issue you added except all it does is generate a log entry (like a comment) into your audit log. It is a great way to record various variables that you are conditioning on to help troubleshoot while you build the rule or later in the event the rule fails down the road.

That aside, is the rule still exiting without action? If so, can I ask if the "push to production" field, is getting set during the transition? If so, could you please add the Re-fetch issue data Action component to your rule just prior your current Condition check. What this does is to avoid any race condition where the automation rule triggers before the field data is updated. Please let me know if any of this does not make sense.