I just received this from Atlassian:
Classic projects will be named company-managed projects and next-gen projects will be named team-managed projects. We heard your feedback that the classic and next-gen names were confusing, so we've chosen new ones that are more clear and descriptive. We will continue to invest and innovate both team-managed and company-managed projects. |
My question for the forum users:
How many of you were confused and requested this change?
I have documentation that refers to these terms. I now have to go in and change my documentation for terms that are confusing to me right out of the gate. Next-gen projects are horrible. Calling them team-managed projects looks more attractive to an inexperienced user. They are likely to select this option and negatively impact my classic environment. Might be what Atlassian wants to happen but I guarantee these name changes aren't going to help my user base.
Tickets transferred from classic to next gen can lose data because classic has items that are not available in next gen.
General users are not aware that this can happens since classic projects do not have this issue. I believe Epic link information is an example.
I'm in another camp. Company managed implies the creator has less control. Team managed would be their default choice. I'll have to look at disabling it. I have internal documentation that will need to be updated as well.
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Get the most out of Jira
Explore the interface and basic Jira terms, then discover how to effectively manage your work.
Learning Path
Atlassian tools and practices for developers
Focus on your development work by using Jira software features and functions efficiently.
Atlassian Certified Associate
Jira Software Essentials certification
Demonstrate proficiency in utilizing essential Jira features and working efficiently with Agile frameworks like Kanban and Scrum.