I am very happy with the NG / Team Managed projects.
There is not much I miss from the Classic projects, and it is much easier to adjust them and event to understand how they work.
From the article I saw in an earlier comment about how to migrate between project types, this is very helpful and detailed, although it shows how much of a major disconnect there are between these two kinds of projects. Hopefully can make this smoother so you don't loose data converting.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
@Bree Davies the new names are much better. Administrative improvements to CMPs are going to be a huge one for us. We have large Cloud and Data Center sites and managing fields, workflows, etc. in a large org is ... hoo boy. Will especially be looking to see the answer to "How can TMPs create config items (fields, workflows, etc) without polluting the CMP admin screens?"
Stop cooking up new ways to rearrange and taped together your over-leveraged data infrastructure and rebuild, upgrade, and re-design it so that the feature set consists of top-notch, well-architected, cloud native code.
Then you'll have a foundation for well-designed and effective features and not have to hype a half-imagined solution that promises change but not progress toward better, cleaner, leaner, operations and not mashups that are just called integrations.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
With this Release, is it also possible to create classic projects with defined schemes from API? We have connected our ERP System with Jira Cloud and this would help so much.
Thanks so much for *fixing* the names. The previous names were *bugs*.
All the assumptions I made upon hearing them were incorrect. It took hours of research to understand that what I needed was the company managed projects (previously the very misleading "classic") and that I wasn't giving up any functionality by so choosing.
In fact I was losing functionality that I needed, as well as wasting much time, by creating a team managed ("next-gen") project.
Next time please think about names a bit more. Naming is hard, and it matters a lot, and this has been a disaster.
Great news. I'm really looking forward to being able to select a template. The development of Jira over the last couple of years has been fantastic. Well done.
Slightly off topic but while we are on the subject of simplified naming one thing that has got me totally confused is "Workflows" and "Workflow Schemes". I understand the concept of a Workflow, but I am totally lost when it comes to "Workflow Schemes." (And I have been using Jira for over ten years now.)
@Chris schemes are the grouping of multiple configuration items that you actually point to a project (in what is now consider the "company managed" project type). They are the backbone of Jira and make it very powerful.
So, for example, with Workflow Schemes, you may have one scheme with 20 different workflows (each one for a separate issue type) and you use that in one particular project that has all of those issue types. Then you might have another Workflow Scheme that has only two workflows with each one shared by many issue types and you use that scheme in three projects that have those issue types. The schemes allow for easy customization where you have certain use-cases that need to apply broadly and you want any ongoing updates to apply everywhere at the moment of the change. And then you have other schemes that are very particular to one use-case and should only affect a single issue type in a single project. You can also make a Test Scheme and apply it to a Test project to test on issues, then when ready for Prod, you point that scheme to your Production project.
Maybe you have been using "Team Managed" projects and since they are very basic and do not allow sharing of configurations, you have not needed the schemes in a while. Some Admins asked for a way to let Project Admins control the full configuration of their project without giving them full Jira Administration... and voila, "Team Managed" projects. I personally would have preferred more bug fixes and features that are needed instead, but there are some use-cases that these basic projects help with.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
R.e. schemes, this might help in visualizing. It's for screens (not workflows) - screens have yet another layer of "nesting". I created this for our internal docs but there's no company info in it:
140 comments