nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation - Transition Issue

Josh Velez

I currently have automations to transition a parent to "Admin Review" when related tasks are completed across separate projects.

Parent is in GEE project

Related tasks are in HEE project

My issue is when I transition GEE project to "Task Complete" it transitions HEE from "Task Complete" to "Admin Review". I need to know if there is a way to prevent this.

Accepted answers

Trudy P Claspill

Hello @Josh Velez

You said you have issues in HEE project with parent issues in GEE project.

Do you also have issues in GEE project that have parent issues in HEE project?

Do you want the automation to run only if the issue transitioned to Task Complete is in the HEE project?

If so, you can add another Condition - a JQL Condition - and use it to ensure that the automation runs only for issues of type Request that are in the HEE project and go through the transition to Task Complete.

Screen Shot 2021-03-30 at 11.33.58 AM.png

All comments

Trudy P Claspill

Hello @Josh Velez

You said you have issues in HEE project with parent issues in GEE project.

Do you also have issues in GEE project that have parent issues in HEE project?

Do you want the automation to run only if the issue transitioned to Task Complete is in the HEE project?

Screen Shot 2021-03-30 at 11.33.58 AM.png

Josh Velez

GEE will always the parent

Trudy P Claspill

It sounded like you said that some automation was causing issues in HEE (the project containing child issues) to be changed when issues in GEE (the project with the parent issues) are transitioned.

In that case, either there is another automation rule affecting that, or this same rule is being applied when issues in GEE are transitioned, and the GEE issues have parents in the HEE project.

The rule that you wrote, with the additional condition I suggested, should constrain it to taking affect only if the child issues is in the HEE project.

Perhaps if you provided some specific examples of what is happening that will help us understand.

Colton.Kosicek

As of now - you would need Jira global administrative capabilities to do a multiple project select option. This will allow you to have an event in your child project to trigger an automation that reviews content that is part of your parent project. Without this multi-select capability (only admins have this function) the automations don't seem to work well.

I use this for my Parent EPIC project for my SAFe team. Stories are contained in the team projects and Epics are all located in one location.

I run a rule for when all children to an epic are complete i move the epic to Ready for Acceptance.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud