Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

clone issue using jira automation

Asaf Horovitz October 12, 2022
we are trying to clone issue to another project but we are getting error 
Can not create issue in project/issue type
10020/10002

2 answers

1 vote
Trudy Claspill
Community Champion
October 12, 2022

Hello @Asaf Horovitz 

Welcome to the community.

Another thing to check is the Actor for the rule. Does that actor have permission to create issues in the destination project?

Are the source and destination projects both Company Managed projects, or Team Managed projects, or not the same?

Asaf Horovitz October 12, 2022

we are trying to clone from "service management" project into "team-managed" 

there is a solution to achieve this kind of clone?

Trudy Claspill
Community Champion
October 13, 2022

There are multiple ways to describe the "type" of a project.

One way is to identify if it is Company Managed or Team Managed. That will display at the bottom of the navigation pane on the left.

Another way is to identify if it is a Software, Service, or Business project.

You have told us that the source project is Service, but not if it is Company Managed or Team Managed.

You have told us that the destination project is Team Managed, but not if it is a Software, Service, or Business project.

Please provide the missing information.

Also, please show us your complete rule, and the details of the Clone action.

Asaf Horovitz October 18, 2022

The source project is "company-managed project"

 

attached screenshot with the automation rule

 

Screen Shot 2022-10-19 at 9.56.54.png

Trudy Claspill
Community Champion
October 19, 2022

I am betting that the response that was provided by @Janakiraman S applies here.

Screen Shot 2022-10-19 at 9.11.13 AM.png

 

It is unlikely that your Service Desk project and your Bug project have the same Issue Types. You need to specify an Issue Type that actually exists in the destination project in the above step in your automation.

If you click on the "Same issue type" pull down you will see the issue types that are available in your "Production Bugs" project.

It is possible that you have some shared Issue Types between the projects. Note, though, that the rule is being triggered for every issue created in the Source project. With the selection you have in the above step, every issue type you have in the Source project would have to exist in the destination project also. If you want to clone only specific Issue Types from the source project, then you need to add a Condition immediately after the Trigger to limit the rule execution to the specified issue types.

Screen Shot 2022-10-19 at 9.18.00 AM.png

Asaf Horovitz October 20, 2022

thanks 

changing the issue type did solved the problem

Trudy Claspill
Community Champion
October 20, 2022

Glad I could help.

If your problem has been solved and your question answered, please mark the post as Answer Accepted to help other community members find the post with working solutions.

0 votes
Janakiraman S
Contributor
October 12, 2022

Probably the Issue Type scheme of the destination project has different Issue Types from the one you are cloning. 

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events