Uploaded image for project: 'JIRA Server (including JIRA Core)'
  1. JIRA Server (including JIRA Core)
  2. JRASERVER-5721

Enhance 'Project Category' functionalty (versions/components/roadmap) and allow nested categories

    Details

    • Feedback Policy:

      JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

      Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Atlassian Update: 23rd December 2015

      Hi all,

      Thanks for participating in this issue, either by voting, commented or just watching. We highly value your feedback in all forms, and through suggestions in jira.atlassian.com is not different. We use this channel often to learn the best we can with how customers use JIRA and how we can continue to improve the experience for as many users as possible.

      We have revisited this issue again recently and wanted to reiterate that there are still currently no plans to implement this suggestion, and it is not currently on any JIRA team’s roadmap at this stage.

      Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Kerrod Williams
      Kerrod (dot) Williams (at) atlassian (dot) com
      Product Manager, JIRA

      One of the configuration difficulities with JIRA and it's 'silo' project structure is how mapping/coordinating across multiple projects is very troublesome.

      One Example of this are an enterprise software product where individual modules are mapped onto projects yet the product as a whole has no central control point.

      Another example is a consulting organization working on several different projects with the same client, or one project with multiple deliverables.

      One fix for this would be to extend the categorizations available for individual projects onto project categories - essentially nesting projects - where each individual project has it's versions and components yet the project category can have a overall view of deliverables.

      Such a feature would quickly create demand for 'views' similiar to those available for JIRA projects today - roadmaps, issues by user, filtering by category, etc.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                wcrighton William Crighton [CCC]
              • Votes:
                209 Vote for this issue
                Watchers:
                115 Start watching this issue

                Dates

                • Created:
                  Updated: