I'm running into an issue with migrating issue types when attempting to associate these to a new project. I haven't come across the issue before and I'm unsure how to solve it.
So I've created an issue type scheme and added the Issue types I want to be associated with the scheme.
When I attempt to associate this with the Project in step 2 of the migration I select the new issue to migrate to.
But then I run into an issue with the components
Any help in how to progress or steps I need to take to rectify this would be great.
Hello @Alexandre Perron check that the project has at least one component created. Once it's there instead of complaining it should allow you to select it and move forward.
The other option is to have a field configuration assosiated to the new issue type and mark the component field as optional.
Hi @Hernan_Halabi__Elite_IT_Consulting_Group_ thanks for responding.
There were already components in the Project active.
The component field is already currently optional
I've also associated the appropriate screen to the components field config
Though my apologies, the Project isn't new, it is an existing project.
I'm trying to create a new 'create issue screen'.
I had no issues with a previous Project we changed.
Hi everyone! My name is Jenny, a Product Manager at Atlassian. After launching Team @mentions in Confluence, we heard a lot of positive feedback from customers that they love how easy it is to @men...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events