-
Suggestion
-
Resolution: Unresolved
-
None
-
8
-
5
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
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.
- is duplicated by
-
JRASERVER-10048 Add support for multi-level project hierarchy
- Closed
-
JRASERVER-12690 I would like it if all configurations, e.g. screens, schemes, custom fields, etc. could be set up on a Category Basis.
- Closed
-
JRASERVER-14180 Ability to be able to get project category repeated.
- Closed
- is related to
-
JRASERVER-747 Dashboard improvements
- Closed
-
JRASERVER-846 Support for subcomponents
- Closed
-
JRASERVER-1410 Allow categorization of projects and use drilldown menu/breadcrumbs for navigating them
- Closed
-
JRASERVER-2954 The project categories management should be improved
- Closed
-
JRASERVER-4199 Category could have tree or hierarchy structure.
- Closed
-
JRASERVER-5615 Allow default dashboard pages to be updated when multi portlet pages are used.
- Closed
-
JRASERVER-5803 Global portals, configurable project portlet, project groups
- Closed
-
JRASERVER-12241 Support for Product Suites / Sub-Projects
- Closed
-
JRASERVER-22451 Show project category on /secure/project/ViewProjects.jspa
- Closed
-
JRASERVER-22509 Projects should be grouped by category
- Closed
-
JRASERVER-4578 Assign more than one category to a project
- Gathering Interest
- relates to
-
JRASERVER-36275 Support for Product Suite
- Closed
-
JRACLOUD-5721 Enhance 'Project Category' functionalty (versions/components/roadmap) and allow nested categories
- Gathering Interest