History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-4578
Type: New Feature New Feature
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Frank Schimmel
Votes: 6
Watchers: 3
Operations

If you were logged in you would be able to see more operations.
JIRA

Assign more than one category to a project

Created: 16/Sep/04 04:01 AM   Updated: Wednesday 03:25 AM
Component/s: Administration
Affects Version/s: 2.6.1 Enterprise
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Duplicate
Reference
 

Participants: Frank Schimmel, Jeff Turner [Atlassian], Kevin Wilson and sensui
Since last comment: 3 days ago
Labels:


 Description  « Hide
SITUATION:
I create project categories from different perspectives, i.e.
1. a framework development and customer projects using its libraries.
2. development projects vs. QA projects vs. customer service projects.
3. a framework development and an QA project for this.

My JIRA project fits in multiple categories, i.e. it is a framework AND it is a development project.

Depeding on my role, I'm occupied with all service projects or with a project's development and QA, and so on.

PROPOSAL:
Allow to associate a project with more than only one category. Then I can configure my dashboard by selecting the category best fitting my point of view.



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Jeff Turner [Atlassian] - 16/Sep/04 06:40 PM
Frank,

If a project belonged to two categories, would it display in the various projects-grouped-in-categories views found in JIRA? It rather breaks the one to many model we've assumed.

With 'roles', I think you could achieve what you want with multiple dashboards in 3.0:

http://confluence.atlassian.com/display/JIRA/JIRA+3+Release+Notes

You could have a dashboard configured per 'role' that you have; so selecting the "dev & QA" tab would show you a dashboard configured with info relevant to that task.

Does that sound like it would solve the problem?


Kevin Wilson - 26/Oct/05 02:03 PM
JT --> "Does that sound like it would solve the problem?"

Nope. There is really no way around having the project list able to be managed in a tree structure. Allowing N...N project categories would allow projects to be properly grouped and displayed.


Kevin Wilson - 26/Oct/05 02:48 PM
I need to clarify. Each project should be allowed to belong to N project categories. Each project category should be allowed to belong N project categories. Granted I have not yet brought up a test enterprise version of Jira (we use Pro) but from the information I have seen on it thus far it seems that a project can only belong to a single category, etc.

sensui - 16/Jul/08 03:24 AM - edited
We have similar needs.
1)Define project categories with options, ex.
project category A
  • A_1
  • A_2
  • A_3

project category B

  • B_1
  • B_2
  • B_3

2)Link project to more than one categories,ex.
Project001 belongs to A_1, B_3.

Thanks