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.

[Boris Georgiev [Appfire] · Accepted solution]

Here's a suggestion:

1. Download a trial of Configuration Manager for JIRA and install it.
2. Create a "System snapshot"
3. Download the snapshot (an XML file)
4. Search for your plugin in the plugins section
5. Check the requiredBy attribute to see where it is used or search for all occurences of a pattern which is the plugin package (i.e. com.googlecode)

This will give you a list of post-function/transitions/validators used and you'll get an idea what exaclty are you using.

Here's a sample of how the plugins section looks like

<plugins name="JIRA Suite Utilities" key="com.googlecode.jira-suite-utilities" version="1.4.9" vendor="beecom AG" vendorURL="http://www.beecom.ch/" requiredBy="//@workflows.2"/>

And here's a sample xml of a workflow validator:

<stepTransitions name="Close" id="71" status="Done" oldStatus="Finished" view="fieldscreen" destinationStep="//@workflows.2/@steps.4" screen="//@fieldScreens.0">
        <validators description="Required fields:
          <b>Resolution</b>    " className="com.googlecode.jsu.workflow.validator.FieldsRequiredValidator">
          <objectProperties name="hidFieldsList" referencedObjects="//@fields.13"/>
        </validators>

[Boris Georgiev [Appfire]]

For anyone interested in our backlog we have a feature which will allow you to view all dependencies between configuration objects in your JIRA instance including plug-in usage.