Automation for Jira cloud - Issue Released

[Amy Bass]

I am trying to create an automation in JIRA to transition an issue to a new status when the fixversion is released. 

I've set up the automation to trigger using Version Released and the action to be transition issue.

When I attempt to turn on the automation I receive the following error: 
The rule has been configured with components that require issues to be provided by the trigger. To run these components you must add a branch for this version or JQL. The following components require issues: Transition issue

Execute this rule when a version is released. You can access the version object in other components by using the 'version' smart value e.g. {{version.name}}

I'm presented with a Version name filter, but cannot figure out what to put in the Version name filter.   I'd like it to run for any versions >  1.*.  I'd appreciate any help with making this automation work. 

[Bill Sheboy · Accepted solution]

Hi @Amy Bass 

It sounds like you may be missing a piece of your rule to access the items associated to the version.  (Please post an image of your rule if I am missing something.)  This can happen when you have placed your action *outside* of the branch structure.

So, your rule might look something like this:

• Trigger: version released
• Branch: for issues fixed in version
  • Condition: maybe add a condition if you need to limit the items transitioning.  For example, abandoned things, stuff already done, etc.
  • Action: Transition the issue to the status you want

Best regards,

Bill

[Amy Bass]

@William Sheboy I agree that I may be missing a piece but I'm not sure what!  Here is a screenshot of what I've been able to configure.  I appreciate any wisdom you may have!

[Bill Sheboy]

Hi @Amy Bass 

I think something got bent/broken in the trigger; maybe some regex stuff was added in the options.  And your test condition appears after the action to perform the transition.

Not sure what is up, so I recommend deleting that rule and starting over.  Here is the example one I just created.  The only thing I didn't add was conditions you might want to include to limit the transition.  I tested it and it worked for me.

I recommend that you save as you add the pieces: add the trigger, save, add the branch, save, add the action, save, add the name and publish/save.

[Amy Bass]

@Bill Sheboy Thank you!  Your advice helped and I was able to get my rule set up successfully!

[Bill Sheboy]

I am glad that helped you.  Please consider marking this question as answered so others can easily find the solution in the future.  Thanks!

[Thomas Fortenberry]

I need help........  

How do I create an automation rule that if I am moving a status from Created to Backlog, I can require that certain fields have been completed, before it will allow the user to transition the issue to a new status?

Thank You

I found my answer... I need to use a validator on my workflows  :)

[Bill Sheboy]

Hi @Thomas Fortenberry 

That would be more of a workflow solution than an automation rule one.  Please search the community posts (or a browser search) for something like "require field before status change", and you may find a few approaches.

Best regards,

Bill

[Mignonne Yap]

@Bill Sheboy Hi, where can I find or how do I create the "For Issues fixed in version" step?

EDIT: Never mind, I found it after further digging. Thanks!