Forums

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

How do I copy fields from a regular project into a nextgen when cloning the issue?

Sigrid Schoepel
Contributor
January 7, 2021

We have a service desk project and engineering uses a nextgen project. There are some service issues that need fixing in the product and are cloned to the nextgen project. I have custom field set up in the nextgen to mirror the ones in the service project. BUT, I cannot copy them as part of a regular workflow and the automations I have set up in the nextgen project to run upon creation of the issue do not copy the fields. I have checked many, many times that I have the right fields and projects in the automation. I've redone everything in two test projects and it doesn't work.

Is it not possible to copy values from a regular project to a nextgen?

4 answers

0 votes
Matthias Gaiser _K15t_
Community Champion
January 7, 2021

Hi @Sigrid Schoepel,

I can think of two ways how you can get to a solution:

  1. Ask the Atlassian Support
    Since no one here seems to know if Automation can/should do that, you could ask the Atlassian Support team for that. And if it doesn't work yet, ask them to open a feature request, so it might work some time in the future.
  2. Use an issue sync app
    I'm part of the team behind the Backbone Issue Sync app. With our app, you can synchronize issues between different projects. I've just tested your use case - and with our app, you can also copy next-gen fields between all the combinations: next-gen to classic, classic to next-gen, next-gen to next-gen.
    I guess the other issue sync apps should also be able to do that, but I haven't verified that.

Hope this helps,
Matthias.

0 votes
Monika Rani
Community Champion
January 7, 2021

Hi @Sigrid Schoepel  As @John Funk Suggested I agree with him. I also don't think so it is possible as next-gen's custom fields are completely independent. I never try like this before. 

0 votes
John Funk
Community Champion
January 7, 2021

Hi @Sigrid Schoepel  - Custom fields created for JSM and Classic Software Projects are not available to be used in Next-gen and vice versa. Custom fields for Next-gen are created independently for ever Next-gen project. 

Sigrid Schoepel
Contributor
January 7, 2021

Right, I know that. I have duplicate fields set up. I have automation set up to copy from one to the other, but it doesn't work either way I try it (automation in the classic to copy to the nextgen or automation in the nextgen to copy from the classic). Are you saying it will never work, that only the core fields can be copied?

John Funk
Community Champion
January 7, 2021

I am not aware of a way to do it. 

0 votes
KAGITHALA BABU ANVESH
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 7, 2021

I think next gen project features are limited.

Those are created for new teams who are going to use jira for their agile with a template pack, Who don't know have complete idea about customisation's.

From NextGen to classic is fine.

NextGen to Nextgen also fine.

But NextGen to classic more difficult or may not possible

Suggest an answer

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

Atlassian Community Events