Update US status if Linked issues are Done

[EL ASSALI Meryam]

Hello, 

I would like to update the status of my user story to "Ready for development" if all the linked issues (blocked by) are Done. 

Here is the rule I've done but it doesn't work unfortunately 

[Evgenii · Accepted solution]

Hi, @EL ASSALI Meryam 

What is written in Audit log when rule is triggered?

And what triggers your rule? Transition of Story or transition of subtask?

[EL ASSALI Meryam]

Hi, @Evgenii 

1- It is mentioned that the ticket in the bloc IF doesn't correspond to the condition which is not true : the issuetype is Story and I push it to Done 

2- The associated User story normally should trigger the rule. 

If the associated issuestype (user story/blockedby) are Done, the US parent should be updated to "Ready for development"

[Evgenii]

try such JQL as second condition:

issue in linkedIssues({{issue.key}},"is blocked by") AND Status = Done

It will check issues, linked to trigger issue, that they all are done

[EL ASSALI Meryam]

Thank you @Evgenii but it's still not working :( 

[Evgenii]

Ok, let's try to describe your rule in a steps.

1. Rule is triggered by transition of issue to Done status

2. 1 check. You check, that issueType = Story

3. 2 check. You check, that issue has linked issues with link type "is blocked by", issue type = Stroy and they all are Done

4. If all conditions are passed, you transition triggerIssue to "Ready for Refinement".

Is it right description of rule?

[EL ASSALI Meryam]

1- Rule is triggered by transition of ASSOCIATED ISSUES to done status. 

2- Correct

3- Correct 

4- The issue is triggered to " Ready for Development" 

Note that there is indeed a transition in the workflow from "Ready for Refinement" to "Ready for Development". The original User Story is on "Ready for Refinement" status before the rule is launched. 

[Evgenii]

Try simple check - search issues with such request:

issuetype = Story AND key = HAL-365

Is your issue shown? If yes, use as 1 condition JQL, instead of field value check.

issuetype = Story

UPD.

I'll try to write a rule and send it to you.

[Evgenii]

Made similar rule, checked. It works 100%.

[EL ASSALI Meryam]

Thank you @Evgenii  but I'm still facing the issue. 

I think the problem comes from the transition from "Ready for Refinement" to "Ready for Development". Because we have some mandatory fields to fill in (Definition of ready) in this transition. 

Do you think that could be the problem blocking the status update? 

[Evgenii]

Well, yes, it can be a problem, but you can set value automatically on transition. Set something default.

I hope Cloud has such option. If not - then set value by editing issue, and after that - make transition

[EL ASSALI Meryam]

I have two options in that validator which is called "DOR-Dev)

- Estimation faite

- US acceptée par l'équipe

I tried to force the checkbox for the "Estimation faite" to False as it is shown below but it's not working. 

in the log, it is asking me to specify the value in a table ! it doesn't make sense

[Evgenii]

Ok, then make it in 2 actions.

1 action - you edit issue, set value of that field

2 action - make transition

[EL ASSALI Meryam]

I'm not sure that what I did below is correct. We cannot edit " a checkbox" , it's not a value to set . I've added two actions but I am sure that the first one is not correct. Do you know how to force the check? I have two options :

- Estimation faite

- US acceptée par l'équipe

I want that one of them be checked to let me the possibility go through the transition. 

Any idea please?

[Evgenii]

Error still the same?

I checked setting of checkbox value, there are not supposed to be problems. It can be set through automation

I made similar rule, it worked fine.

[EL ASSALI Meryam]

yes still the same error. 

What is the type of the field "Flagged" on your side? is it a checkbox? 

on my side, the error is still on the Field DOR-DEV which is a checkbox. 

[Evgenii]

Yes, I used to check, that rule is working, checkbox field.

[EL ASSALI Meryam]

I found the issue ! it comes from the field which was not added to the project :( So automatically it was known in the transition. 

Many Many thanks @Evgenii for your support ! it was remarkable ! 

[Evgenii]

Hooray, you made it! Congrats!

Glad, that I helped you. It was an interesting quest :)