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

Moved all data from one project to another and now automation is not working

eric caprio

I moved all data from one project to another because I was moving the project from a team based to company based. The new company based has built in automation around having a story create sub task code review and sub task QA as the story moves along.

I am not getting this error below... would my solution be to export all the stories, delete them and re-import?

Error creating issue
Issues with this Issue Type must be created in the same project as the parent. (project)

Accepted answers

Trudy P Claspill

Hello @eric caprio

Welcome to the Atlassian community.

It is great that you provided us with the message from the Audit Log.

In order to decipher why this message is occurring we need you to also:

1. Provide the entire audit log entry.

2. Provide screen images showing us the entire rule

3. Provide screen images showing us the details of each step in the rule.

Without that information we have no way to conclusively debug the issue.

Based on the message and the fact you said the rule is creating subtasks, that suggests that the subtask creation is trying to be executed in a project other than the one where its parent issue exists.

All comments

Pedro Lucena

Hello how are you?
I'll leave a checklist for you to do

Check filters
Check whether items are present in the permission scheme
Have you tried implementing global automation?

Trudy P Claspill

Hello @eric caprio

Welcome to the Atlassian community.

It is great that you provided us with the message from the Audit Log.

In order to decipher why this message is occurring we need you to also:

1. Provide the entire audit log entry.

2. Provide screen images showing us the entire rule

3. Provide screen images showing us the details of each step in the rule.

Without that information we have no way to conclusively debug the issue.

eric caprio

Hi there, please see attached for more information. I am guessing this might have to do with only being applied to two projects, in which the one these stories started in are not one of those two projects (created in a Darwin Analytics project team based project - which had all the data moved to Analytics project company based project.

Screenshot 2024-07-19 at 10.44.59 AM.png

Trudy P Claspill

Based on the image you provided the issue that triggered the rule is AND-43. That is an issue in your project named Analytics.

In the step where you are trying to create the subtask you have specified that the subtask should be created in the project Innovations.

That is not allowed. Subtasks must be created in the same project as their parent task. That is the reason for the Error in the log.

You need to change the subtask creation step to create the issue in the Same Project as Trigger.

Screenshot 2024-07-19 at 8.39.02 AM.png

Or you need to eliminate the Analytics project from the rule Scope.

eric caprio

thank you! I did not know that was within the action. All fixed.

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