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

Jira Automation - Creating a clone ticket from company-managed to team-managed

Abi Williams

Hey everyone i was wondering if anyone can assist me with an issue.

We have two teams who are working on the same project. One team uses team-managed and the other team uses company-managed. We havent changed anything from default tickets (tasks, stories etc) minus one were it is called release deployment. I have changed a few of the columns but i am not sure

I am trying to create an automation where if something on company-managed is created under an parent (epic) it will be cloned onto the team-managed project using this logic below. This is coming from company-managed board.

Screenshot 2024-05-09 133226.png

Screenshot 2024-05-09 140158.png

I currently have a testing project (our old board) that is company-managed but every time i create it i get this error: " Can not create issue in project/issue type 10112/10014" I aint sure what this means at all because i aint getting enough info to understand what this means.

Screenshot 2024-05-09 134348.png

Any help would be grateful. I aint the biggest Jira expert so i will need info on how find things if you require additional info.

Accepted answers

Bill Sheboy

Hi @Abi Williams -- Welcome to the Atlassian Community!

Team-managed projects (TMP) have their own configurations and types, different from the shared ones for company-managed projects (CMP). That error indicates using the Issue Type of "Same issue type" will not work with the TMP, and so it shows the specific issue type id values which have the problem.

Please try selecting the specific issue type from the dropdown list to see how that helps.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Abi Williams -- Welcome to the Atlassian Community!

Please try selecting the specific issue type from the dropdown list to see how that helps.

Kind regards,
Bill

Abi Williams

Morning @Bill Sheboy

The company-managed project will use both stories, tasks and spikes for this project hence why i wanted to keep it as the "same issue type" because i figured it will copy over easier.

I tried checking to to task as a test and go another failure. Apparently it didnt like the story points so i removed this too.

It now looks like this.

Screenshot 2024-05-10 094510.png

And these were the errors:

Screenshot 2024-05-10 094242.png

Bill Sheboy

Regarding story points:

company-managed projects use the "Story points" field, and
team-managed projects use "Story point estimate".

Please select the correct field from the dropdown list for the TMP issue, supplying the value as {{issue.Story points}} to copy it. However...

Regarding issue types, this is a known problem for cloning issues between TMP and another project...even two different TMPs: https://jira.atlassian.com/browse/AUTO-410 The defect is intermittent: in my test site, the Task issue type works but the Story one does not :^(

Two possible work-arounds to try:

Instead of Clone Issue, use the Create Issue action, manually selecting and copying each field. This will require using an if / else structure on the trigger issue's type so the correct issue type may be selected explicitly in the Create Issue action.
Using the same if / else structure on issue type, except call the REST API create issue function with the Send Web Request action

Abi Williams

Afternoon @Bill Sheboy

TIL about story points. They don't specifically highlight it easier between team vs company-managed projects in regards to fields but it might be being picky!

AUTO-140 would explain the issue then. Thank you for finding this.

I have figured out to do method 1 and it is working perfectly. Thank you very much! Only thing i am not sure about is how to do subtasks on tasks? Do you have any advice on how to do this?

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