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; } } }

move parent (living in another project) from one state to another

Francisco Navarro_zsedh7

Dear community,

I'm trying to create an automation for a project in jira that moves my "Project" issue based on the movement of epics that live in different projects, these epics are connected with the "parent" field to the main project.

I need the issue indicated in the parent to be moved to a particular state when the project epic goes to "in progress". I created the following but I don't know where I'm failing because my "project" issue doesn't move. Attached images.

Accepted answers

All comments

Bill Sheboy

Hi @Francisco Navarro

For an automation question, please also post an image of the audit log details showing the rule execution. That will provide context to see which steps in the rule processed.

Also, what is the scope of your rule: single-project, multiple-project, or global?

You describe the issues are in different projects, and so the rule will likely need multiple-project scope. Your Jira Site Admin will need to help make that change in the global automation area.

Kind regards,
Bill

Francisco Navarro_zsedh7

Also, what is the scope of your rule: single-project, multiple-project, or global?

I first tried from the project that "triggered" the action to move the parent project from a "not started" state to a "site candidate", but in the "transition" action the final state (site candidate) did not appear, so I set the automation for "multiple projects", and in this scenario the final state I needed did appear.

I attached the automation log, thanks!

Bill Sheboy

To confirm, is the rule now working as you expected?

Trudy P Claspill

Hello @Francisco Navarro

Looking at the Audit log it indicates the rule was triggered by issue CDNS-3211, and that issue did not match the first condition (issue type = Epic) so the rule stopped running. Is that correct functionality? Is CDNS-3211 indeed not an Epic type of issue?

What happens if you transition an issue that is an Epic and has a parent issue in a different project?

Jeffrey_Denton

Is the automation rule global, for both projects?

Jack lee_6p7nas

Based on your description, "Project" issue when an Epic in another project transitions to the "In Progress" state. The automation you’ve created likely needs a few tweaks.

Here are a few things to check:

Trigger Configuration: Ensure that the trigger is set correctly. It should be based on the Epic issue type transitioning, not the "Project" issue. For example, the trigger could be set as "Issue transitioned" and filter it specifically for the Epic issue type moving to "In Progress."
Condition for the Parent Link: Make sure you're using the correct JQL (Jira Query Language) to check the parent link, such as parent = <Epic Key> or something similar. You might need to reference the parent field properly to ensure the correct project issue is selected.
Action Configuration: Double-check the action that moves the "Project" issue. Ensure that it’s set to update the status of the linked issue and not just the Epic.
Permissions: Make sure the automation has the necessary permissions to move the issue within the relevant projects.

If everything is set up correctly and it’s still not working, you can also check the audit log for errors that might provide further insight into where it’s failing.

Trudy P Claspill

@Jack lee

Welcome to the Atlassian community.

1. The Issue Transitioned trigger allows you to specify only the starting and destination status. You cannot specify within the trigger the type of issues to which you want the trigger to apply. You have to add a Condition after the trigger to check the Issue Type of the trigger issue.

2. There is no need for a Condition to check the Parent link. The For Parent step determines if the Parent field of the trigger issue has any data. The Issue Type Hierarchy determines what type of issue can be the parent of another issue. If the hierarchy is configured to allow only "Project" issue types to be parent of an "Epic" issue, then this branch will execute only when the trigger issue (an Epic, per the previous condition) has a parent and that parent will be a "Project" issue.

3. Given that the Action to transition the issue is nested within the For Parent branch, that action will be applied to the Parent of the trigger issue - the parent "Project" of the "Epic". Additionally that action has no direct configuration option for specifying the type of issue to which it should apply.

Francisco Navarro_zsedh7

No, I had to add it to the parent project because the destination state I needed to move to did not appear. Initially, the automation was built locally, but since the destination state information was not provided, I added the project.

Jeffrey_Denton

For this to work it has to be a global automation. Please check to make sure its a global operation as I believe you are using this between two projects and it would have to be global to work.

Jeffrey_Denton

Here is my automation for moving Epic (parent) based on Child Status. My epic only transitions if all child tasks are in that status. I have a automation per transition. The first transition moves the epic, but every transition after that is based on if all children have the same transitioned status.

screencapture-rk-industries-atlassian-net-jira-settings-automation-2025-01-19-21_40_42-edit.png

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation