
| Key: |
JRA-3813
|
| Type: |
New Feature
|
| Status: |
Resolved
|
| Resolution: |
Duplicate
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Jim Caprioli
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
JIRA
Created: 25/May/04 02:01 PM
Updated: 27/May/04 05:56 PM
|
|
| Component/s: |
Backend / Domain Model
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
|
If I could organize components in a tree like structure ( a Parent : Child type of link ) JIRA would be an excellent tool to implement issue management for systems management as well. In software development the issues are linked to sources in CVS in systems management they must be linked to configured items like a server, printer, installed software package and so on.
The request is for organizing components in a tree.
|
|
Description
|
If I could organize components in a tree like structure ( a Parent : Child type of link ) JIRA would be an excellent tool to implement issue management for systems management as well. In software development the issues are linked to sources in CVS in systems management they must be linked to configured items like a server, printer, installed software package and so on.
The request is for organizing components in a tree. |
Show » |
|
What effect do you envisage hierarchical components having? If I have:
ComponentA
ComponentB
ComponentC
Do you just want the Components drop-down list to be suitably indented? Can an issue be assigned to ComponentC, or is that just a grouping? Or should a search on a parent component also include results for all subcomponents?
I've marked this as duplicate of JRA-846 - please add further comments there.
Cheers,