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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to trigger a rule when linked issue status change

Dear all,

I have a wierd scenario where I could not find a way from cloud to do it while it was possible from server side.

I have the following issue configuration below :

3KRFUN4xMA.png

As you can see above I have 2 reference Links "Refer to incidents" and "demands"

The issue which is listed in "demands" link as been trigger to DONE from an other automation rule.

Question :
Is there a way to trigger a rule at this issue level only when the issue in "demand" links has change to DONE

Idea is that when the issue in that link change to DONE, we need to trigger all linked issue in "Refer to Incidents" to status COMPLETED

Any idea how to do this trigger ?

regards

2 answers

Hi @serge calderara  

I know that this can be done with an additional plugin, like ScriptRunner. You could for example have ScriptRunner listen to the update event and then set a value in a custom field. Then you use the built in automation to run once the custom field gets updated to this value.

HTH,
KGM

P.s. I am not affiliated with ScriptRunner.

0 votes
Daniel Ebers Community Leader Jan 25, 2021

Hi @serge calderara

one approach would be to have two rules like the following:

For project SHW:

grafik.png

For project SD:

grafik.png

To summarize:

As soon as in project SHW an issue is transitioned to done in it's linked issues of type "is demanded by" a label is set.

The rule for project SD listens for the appearance of label "Notify". As soon as this is given all linked issues with type "Refer to incidents" are transitioned to done (given you have status completed also, you could also transition to that one or any other that seems suitable).

In case this was understood correctly - what will happen to SD-4508 issue? Is this closed manually?

Could you confirm this is understood correctly so far?

Regards,
Daniel

Hello @Daniel Ebers , SD-408 should also be set to completed as long as the issue SHW-233 is set to Done.

I do not understand what you mean by this label Edition ? can it be the resolution field instead ?

In addition in case we monitor the label field from SD project as you propose, the rule might trigger many time if this label field is changed from other type of issue no ?

The link https://community.atlassian.com/t5/Jira-questions/How-to-make-a-OR-condition-in-Jira-Automation/qaq-p/1587067

Was my initial post where I was trying to make a kind of recursive linked issue to get same result but could not succeed so far..

Regards

Serge

Yes, it also works without labels - here is what I can come up with, using two rules.

For "SHW" project:

grafik.png

For "SD" project:

grafik2.png

 

In a test, it worked very well.
Please note, for the second rule 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." must be checked.

hello @Daniel Ebers ,

I guess the first rule should be executed from SHW project and the second rule from SD project correct ?

I do not understand how the second rule will be trigged automatically if executed from project SD ?

Thanks for clarification

I just draw a full picture just to be sure we are on same path :

https://1drv.ms/b/s!AuPzV8ZG3v-2lUtuKHBLxAHRnTn1?e=4pRohg 

Daniel Ebers Community Leader Jan 26, 2021

Yes, the first rule is with SWH project. It says: when the issue is transitioned to done it will check for any issues with link type "is demanded by". A finding will be transitioned to "done".
Then the second rule (in "SD" project") catches.
This one says: as soon as an issue is transitioned to done (coming from first rule) all linked issues with type "refer to incidents" are transitioned to done (or whatever status is appropriate).

I hope it makes sense now.

hello @Daniel Ebers  thanks for clarification but when you said :

"This one says: as soon as an issue is transitioned to done (coming from first rule) "

how do I know the rule in project SD is trigged from first rule and no others ?

Daniel Ebers Community Leader Jan 26, 2021

To my knowledge there is no such distinction. Why do you consider this important to your use case?

hello @Daniel Ebers , simply because I do not want that this SD rules is trigger a lot of count time 

You mentionne earlier about this check box to check in order to allow rule to be trigger froman other rule. On whish rule this check box need to be set ?

Daniel Ebers Community Leader Jan 26, 2021

I see, but in this place they are needed to do the automation. Otherwise parts would be missing to be executed - at least in this architecture of the rule.

As for the second question - yes, the rule in the "SD" project must be checked for allowing to be called from other rule - here specifically in order it can be executed from the previous rule (coming from "SHW" project).

thanks, I will give a try and let you know

Hello @Daniel Ebers ,

Here is my test result based on your sugestion of 2 rules.

What is happening is that the first rule execute normaly as it should but the rule in SD project did not execute at all, it has not been fired even with the check box in this second rule checked.

Jw2vdKVMS9.png

As seen above related incident remains in progress

Here is below the complete second rule :

s30jEne8aa.png

Any idea ?

I noticed that if I transition one incident manually to completed, I have a screen popup that user need to filled up. Does that screen prevent the rule to fire ?

Daniel Ebers Community Leader Jan 26, 2021

Could you please show the complete setup of both rules (= like in the last screenshot - just for both rules)?

hello @Daniel Ebers , here is below the first rule

chrome_tsajlRAcFi.png

Daniel Ebers Community Leader Jan 26, 2021

It is getting a bit complicated I must admit :) But for the moment I believe the problem could be in first rule we are transitioning to status "Completed" but in second rule we are listening for status "Done".
So the second rule would have to start with "When: Issue transitioned TO Completed" :)

If this also does not work out a look into "Audit log" (below Rule details) should tell what is still missing.

hello @Daniel Ebers , seems it has work by changing to completed status :-)

Thanks you so much

By the way remaining question :

Q1 : is it true that there is not count limit execution of rule IF it is project rule vs global ?

Q1 : Is it also true that rule execution are queue when running ? let say if you have 10 rule executing and the last one is more important that the others, it will be anyway executed as the last one ?

regards

Daniel Ebers Community Leader Jan 27, 2021

Sure, you're welcome. It was really something to learn and to try.
If I understood everything correctly Dirk will present an alternative solution in here:
https://community.atlassian.com/t5/Jira-questions/How-to-make-a-OR-condition-in-Jira-Automation/qaq-p/1587067

You will have to check which one suits better.

For your remaining questions (Q1/Q1) I'd propose to copy them over to a new thread. This here is quite long (probably no one else will read completely through it), I cannot answer it in detail (Q1/Q1) and others should also have a chance to reply.

Glad the main topic with the rule worked out, nice!

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you