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,465,146
Community Members
 
Community Events
176
Community Groups

I have a change request if i modify the Subtask status to In development then Parent task is In Deve

Hi,

Once i create the change request in that i have created a Subtask as well.

If i change the Subtask status from Ready for Approval to In Development

then Parent change Request Status also modify to In Development

I want to create relationship such a way that if i change the status in the sub task then the same status need to be there in the Parent change request

Can some one will help me how to achieve the same functionality.

Thanks,

1 answer

1 accepted

2 votes
Answer accepted

Hi @Sreenadh 

This is a pretty common use-case that can easily be resolved using Automation for Jira.

At its simplest form, you can create a rule on the desired Project to be triggered when a sub-task is transitioned.

  • When: Issue Transitioned from Ready for Approval to In Development

Add a condition of Issue Type = Subtask

  • IF: Issue Type equals Subtask

Now, even though the issue that triggered the automation is the sub-task, the conditions and related actions should be executed for the parent of the sub-task. Therefore, Go into "Branch Rule / Related issues"

  • For Parent
    • Then (Action) — Transition the issue to: Copy from Trigger Issue (since the status is the same according to your question for both subtask and parent issue).

*The Branch Rule/Related Issues would look something like this:

 

image.png 

 

 

Best regards,
Hamza

Hi @Hamza Chundrigar 

Thanks for your response.!

I have update as per your justification but it is not working as expected.

Please find the attached screenshots .

1.PNG

@Sreenadh can you please post a screenshot of the automation audit log as it allows us to review execution data for the rule such as when the rule was triggered, the final result of the execution, and any actions/error details.

It looks something like this:

Rule config screen in Jira. "Audit log" button is highlighted to emphasize its position beneath the "Rule details" button.

Sure here it is.

4.PNG2.PNG3.PNG

Thanks for providing those screenshots, they were helpful.

So there's an approval step in the workflow, where someone needs to approve the issue in order for it to transition from Ready for Approval to In Developmentcan you confirm if this is the case?


No transitions found for user. Ensure that the rule actor has permission (including issue security levels) to see issue and perform transitions

If that is the case, then it's likely that the rule actor which is Automation for Jira does not have permission to approve and therefore transition the (parent) issue to In Development.

Another possible reason for this rule failing is when there is a missing transition from the target issue workflow, going from the current status (ready for approval) to the new status (in development) in your parent issue's associated workflow — however, this does not seem to be the case.

@Hamza Chundrigar 

So there's an approval step in the workflow, where someone needs to approve the issue in order for it to transition from Ready for Approval to In Developmentcan you confirm if this is the case?

Yes Exactly correct, Change Request Approver need to approve the request then it will move to In Development.

Could you please provide me how to achieve the same

Sorry for late reply it is my late night time.

Thanks,

No worries @Sreenadh 

I can provide you with a method on how you might be able to achieve this, but before I do, I want to bring our attention from the tooling aspect over to the requirements process.

Yes Exactly correct, Change Request Approver need to approve the request then it will move to In Development.

The reason why your rule is failing is because the rule actor (Automation for Jira) is not the appropriate Change Request Approver. In other words:

  • Subtask SDPD-91 moves to In Development however the Parent Issue SDPD-90 is still sitting in Ready for Approval (but has not been approved yet)
  • Automation for Jira tries to move SDPD-90 to In Development because it's child issue SDPD-91 has moved to In Development, as per our automation rule.
  • But because Automation for Jira, the actor, is not the appointed Change Request Approver — it fails to do so because it is being blocked by a workflow condition.

 

Now to my question:

If the Change Request Approver is the person who should be approving the request, then why are you trying to bypass that with Automation? Wouldn't that create a process inefficiency?


There is a workaround, but I highly recommend you reconsider your process first before implementing this.

One workaround could be that you update your project's workflow associated to the parent issue. You could create another transition (similar to the approve transition) that goes from Ready for Approval to In Development but do not add an approval step to this workflow transition. This should allow Automation for Jira to take this path and update the status as per the automation rule.

Tip: As an added measure, you could also add a Hide From User Condition to this new workflow transition. What this condition does is that it hides this transition from the user (humans) so that they won't be able to select and bypass the approval step. However, it remains available to Jira Automation, scripts, remote API calls, post-functions, etc.

image.png

 

Best regards,
Hamza

Hi @Hamza Chundrigar 

One workaround could be that you update your project's workflow associated to the parent issue. You could create another transition (similar to the approve transition) that goes from Ready for Approval to In Development but do not add an approval step to this workflow transition. This should allow Automation for Jira to take this path and update the status as per the automation rule.

Yes it is working fine and i have implemented the same.

Thanks,

You're welcome @Sreenadh 

Please mark the answer as accepted so that it can help other community members by making it easier for others to find relevant content and answers.

Best regards,
Hamza

Suggest an answer

Log in or Sign up to answer