Can I convert a Next-Gen project into a Classic project?

[Mathias Timonen]

I'm curios if I can convert an existing Next-Gen project with issues and settings into a Classic project? Say, I'm unhappy with the Next-Gen feature set and would like to access the features that are only available to Classic projects, which I'm used to. Obviously, I would make a trade-off and lose the features that are only available on Next-Gen, but ultimately that's a trade-off I might be willing to do in certain circumstances.

If that's not possible, is it possible to export issues that exist in a Next-Gen project, create a Classic project and then import them there?

You probably notice what I would like to achieve, so if there's any other way to get existing issues and some settings, workflows, etc. from Next-Gen to Classic, I would be more comfortable with starting a new project with Next-Gen if I would know I can convert it to a Classic one if I really want to access some features I might end up missing from my experience with Classic.

[Tarun Sapra · Accepted solution]

Hi, You should click on retaining reporters and assignee otherwise you would loose them, this happens if the new field configuration scheme has reporter required and the old reporter no longer has permission to be the reporter anymore.

To be honest, I don't like the whole IssueType migration process, I have lost some data on production becasue of the poor user experience and had to sync with backup using a script, i also reported the matter of poor UX to Atlassian and they created this ticket -

https://jira.atlassian.com/browse/JRA-36801

[Alex Perez]

Hi!

In all my attempts I have used the "retain" option, but the migration assistant doesn't allow me to continue to the next screen because "reporter is mandatory".

Please note that there are no changes in permission scheme (users that could be assigned or report issues will remain having this permission) nor in the field configuration scheme (reporter/assigned is a required field before and after config migration).

Any clue why jira is asking me to overwrite reporter and assignee when changing issue type scheme?

[Alex Perez]

Hi again :)

Just made a copy of the Field configuration scheme, and changed the reporter/assignee to optional. Then applied this scheme to the project.

Now the Issue Type scheme migration assistant lets me change the scheme, retaining reporter/assignee. Once the migration is completed, I could change the Field configuration scheme back to the original.

I don't understand the relationship between issuetype scheme changes and field configuration screen config :?

[Tarun Sapra]

When you change the IssueType Scheme, the new issuesTypes are validated against the field configuration, so if the reporter if mandatory in the field condiguraiton that results in migration failing as the validation of the issueType with field configuration enforces the reporter to be present even on older issues which might not have a reporter.

[Alex Perez]

At this point, I think that I'm hitting these bugs:

https://jira.atlassian.com/browse/JRA-16476

https://jira.atlassian.com/browse/JRA-16441

If I'm trying to change only the IssueTypeScheme, and the permission scheme remains the same in the project .. why Jira migration wizard is asking me what to do with original reporter and assignee?