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?
Hi @Sigrid Schoepel,
I can think of two ways how you can get to a solution:
Hope this helps,
Matthias.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.