Add an easy way to find all team-managed projects / Allow Project list to be filtered by Type (Company-managed, Team-managed)

XMLWordPrintable

    • 16
    • 13

      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.

      We understand that our decision may be disappointing. 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


       

      Suggestion: Allow Jira Administrators to filter the Project list on instance by its type (Company-managed / Team-managed) 

      Workaround

      Manually add company-managed / team-managed as a project category and then filter by the category. Add, assign, and delete project categories

      Original Description

      Currently there is no way to easily distinguish which project is classic and which is next-gen  by just looking at the list on projects view.

       

      The source of this suggestions: https://community.atlassian.com/t5/Next-gen-questions/Easy-way-to-find-all-next-gen-projects/qaq-p/1020486

       

      It would be great to have an additional column to distinguish project generations.

            Assignee:
            Unassigned
            Reporter:
            Jakub Sławiński
            Votes:
            41 Vote for this issue
            Watchers:
            29 Start watching this issue

              Created:
              Updated:
              Resolved: