nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JIRA Classic gone: each new project creates new workflow and issue type scheme, is there a way to stop it?

Jennifer Fricke

We create hundreds of projects a year within OnDemand. With JIRA Classic gone, every time we create a new project a new workflow and issue type scheme is created, which we nearly always change to a standardized workflow and issue type scheme.

There are now all of these orphaned workflows and issue type schemes that we never use and have to manually delete to clean up.

Is there a way to stop the automatic duplication behavior?

Thank you.

Accepted answers

All comments

Jobin Kuruvilla [Adaptavist]

I agree. Not sure why this behavior, which IMHO is a bad practice, is enforced.

overdrive64

I agree. The new behavior is weird.

Elisa [Atlassian]

Hi all,

We are aware of this problem and we have already created a suggestion report for the dev team (JRA-39966). Please feel free to add your comments and vote for it to make it more noticeable to our developers. Also refer to Implementation of New Feature Policy for more information on Atlassian's approach to the development of these improvements.

Please let us know if we can help you any further.

Cheers!

Gareth Blain3

I agree with the above comment. This is a badly thought out change and it took me as mentioned about 5 mins per new project to "Fix" the damage it creates. >:-(
Anyway I thought I would comment for future users as while trying other methods to fix this issue (until they put it back as an option) I discovered that if you right click on the new project link (to force it to open in a new window/tab rather than a JS & AJAX popup it opens a basic screen with no option to select schema types etc and when saved the final project uses the default schema. If this isn't the one you want it's still a LOT easier to then change it to what ever schema you want without the need to go deleting all the extra unique ones created with the new "default" method. smile
Hope this helps!

Paul Clegg1

I can't seem to do this on our onDemand it just reopens the Dashboard or current page that I'm on. Is there a specific page you're looking at?

Gareth Blain3

I have clicked on the settings cog icon (from an admin account) and then in the "JIRA ADMINISTRATOR" drop-down that appears I have clicked the "Projects" link. On the new page (which should list your projects) I then have a [+ Add Project] button towards the top right. The link that that button has is something like "[domain.com]/secure/admin/AddProject!default.jspa?....". For me right clicking on it the link in Firefox and Chrome and select "Open in a new Tab/window" and it will open a new page that asks you for the new project's: "Name", "Key" & "Project Leader" with an option to import at the bottom and [Add] button & "Cancel" link below that. I believe if you just create a valid URL using your domain and the above URL minus the domain bit and "..." at the end it will go to the correct page.

Paul Clegg1

Awesome, cheers for that! I can confirm it works with [domain.com]/secure/admin/AddProject!default.jspa

Solin Phann

Let's be short: BRING BACK JIRA CLASSIC!

TIA!

Shahram_Monshipouri

I agree, JIRA Classic was so useful.

Arun Rao1

I agree.

Sandra Axelsdót

I agree! it's fatal not to have JIRA Classic anymore.

Solin Phann

Thank you to the JIRA team for bringing back JIRA Classic smile

SeanM

I created a project this morning, bemoaning once again the loss of JIRA Classic and the extra work that causes for me.

I created a project this afternoon and, blinking twice in disbelief, see JIRA Classic is back! Well done!

Lee Correll

And now...it's gone again in Cloud?

SeanM

Yup. Seems it is. I know it was there a few days ago. They must have just removed it.

SeanM

I just checked the What's New site (https://confluence.atlassian.com/display/Cloud/What's+New) for the last few weeks and didn't see any mention of changes to the create project functionality. Hopefully one of the types they do provide will be as clean as "Classic" was. Frankly, I'm not bothering to check because I just don't want to have to waste time cleaning up all the totally unnecessary workflows and etc that they're likely to create. You know, exactly the same problem they created for us last time they removed the "Classic" option. *You'd think they'd learn.*

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud