Atlassian Update - August 2024

Hi everyone,

Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future.

Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.

Regards,

Jira Cloud Product

With the removal of the JIRA Classic Project Template when new projects are created a new Issue Type Scheme and Workflow is also created, instead of the project inheriting the Default Issue Type Scheme and Workflow for the instance.

This causes additional work for users who already have a Default Issue Type Scheme and Workflow implemented and want to use that for all new projects, as users will have to switch back to the Defaults after the project gets created (and delete the newly create Issue Type Scheme and Workflow if they don't want to use it).

When creating a new project JIRA should give users at least three different options as for the Issue Type scheme and Workflow for the new project:

1. Inherit the Default Issue Type Scheme and Workflow.
2. Give users the option to select an existing Issue Type and Workflow.
3. Give users the option to create new Issue Type Schemes and Workflow.

This will reduce friction when creating new projects.