Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,812
Community Members
 
Community Events
176
Community Groups

Trigger automation rule by transition instead of status

Hi all, 

At my client we like to achieve the following with an automation rule:

We would like to trigger an automation rule based on a self-transition in the workflow. In this case we would like to create a story from a bug, using a self-transition.

For example:

SCR-20221128-l68.png

  • Status: To Do
    • Self-transition: 'Create a Story'
  • Status: Intake
    • Self-transition: 'Create a Story'

This created a workflow button on the top of a bug.

When clicking the 'Create a Story' transition button we would like to trigger an automation rule that will create a new story and link it to the bug.

SCR-20221128-l8n.png

The automation rule is configured as follows:

SCR-20221128-laq.png

This causes the following behaviour:

When the bug in status 'To Do' and you click the 'To Do' workflow status again. It creates a story and links it. We only want to create a story when the 'Create a Story' transition is being used.

Do you guys have any clue on how to configure this?

 

Thanks in advance!

 

 

1 answer

0 votes

Hi @Sander Voskuilen -- Welcome to the Atlassian Community!

Your advanced compare is referencing a specific status value's workflow transition in changelog, but I do not believe that is possible yet. They have information at the field level only.  And so those expressions may be evaluating null to null, and so always passing.

There is an automation suggestion to support triggering on specific workflow transitions: https://codebarrel.atlassian.net/browse/AUT-993

A work-around would be to set a field value on that transition in workflow, possibly using a marketplace addon for scripting, and then test for that value in a condition.

Kind regards,
Bill

Hi @Bill Sheboy ,

Thanks for reply and mentioning the codebarrel request. I will look into this!

For now I used the workaround to hide the current status the issue is in via a JSU option: value field listed in this article at the bottom: Is there any way to hide current trasition In All-... (atlassian.com)

This way the To Do and Intake status is not visible and this solves my 'problem'.

Thanks!

Like Bill Sheboy likes this

Suggest an answer

Log in or Sign up to answer