Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

I need : When a "ticket: clone by" is in an active sprint, clone changes status

Patrícia Gomes March 22, 2022

I need that: on the IT board, when my ticket is in an active sprint, the Jira service management request clone changes status.

I got it working with the sprint field change. But I need it to know that it is an already active sprint.

I was trying it this way, but I don't know what to put in this expression, or if there is another way to make this condition
Can anyone help?

Thanks!

 

Captura de ecrã 2022-03-22, às 15.54.52.png

1 answer

0 votes
Ste Wright
Community Champion
March 26, 2022

Hi @Patrícia Gomes 

Can I clarify the logic is...

  • If a Sprint starts...
  • And it has a linked JSM ticket...
  • Update the JSM ticket's status?

If yes, I found it took two Automation Rules to achieve this.

The Sprint started trigger needs to relate to certain branches - namely For Issues in the sprint. I found that this meant further branching into related linked issues was not possible.

So I created two rules...

  • Rule 1 - Populate a custom field that the sprint started
  • Rule 2 - Transition the linked Issue based on the custom field updating

 


Rule 1 - Sprint Starts

Prerequisite:

  • Create a custom field, to confirm a Sprint has started. You could use a Select List, Checkbox, etc
    • As an example, the rules below use the custom field name Sprint has started

Rule:

  • Trigger: Sprint started (choose a board)
  • Branch: For Issues in the Sprint
    • Edit Issue: Sprint has started = Yes

 


Rule 2 - Transition Linked Issue

  • Trigger: Field Value Changed - Sprint has started
  • Condition: Issue Fields Condition - Sprint has started = Yes
  • Branch: For Linked Issues (is cloned by)
    • Condition: Issue Fields Condition - Project = <<Project>>
    • Action: Transition Issue - to <<Status>>

Then, set Rule Details to...

  • Check the checkbox - Check to allow other rule actions to trigger this rule. Only enable this if you need this rule to execute in response to another rule.

^ This last step allows Rule 1 to activate Rule 2

 


This worked for me. You could also refine the rules further if needed - for example...

  • Only update the Sprint has started field if it's a specific Project or...
  • Only updated Sprint has started if it wasn't already in Yes (if Rule 2 should only activate in the first Sprint an Issue was in)
  • ...etc

 


Let us know if this works for you, or if you have any further questions!

Ste

Suggest an answer

Log in or Sign up to answer