[#JRA-2047] Hierarachical versioned components, with cross-referencing

JIRA

Hierarachical versioned components, with cross-referencing

Created: 17/Jul/03 06:54 PM Updated: 15/Jan/08 03:39 AM

Component/s:

Project Management

Affects Version/s:

2.4 Enterprise

Fix Version/s:

None

Time Tracking:

Not Specified

Environment:

Standalone

Issue Links:

Part

This issue incorporates:

JRA-2744 Version information for components

JRA-1072 Shareable subprojects

Reference

This issue relates to:

JRA-846 Support for subcomponents

Participants:	Alexey Efimov, Jeff Turner [Atlassian], L. Vermeulen, Martin Smyth and Uwe Goetzke
Since last comment:	17 weeks, 4 days ago
Resolution Date:	21/Jun/04 12:04 AM
Labels:

Description

« Hide

What is really missing from JIRA from our point of view is to be able to create component hierarchies within a project and to version components rather than an entire project. In addition, a component in one project should be able to be 're-used' in another by cross-referencing to that components project (the one in which it is really managed and developed). If this were implemented we would also like to be able to indicate version dependencies, and generate compatible version graphs, etc.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Martin Smyth - 17/Jul/03 06:56 PM

Thinking longer term. It would be nice to be able to move a component from one project to another - as often happens when refactoring.

[ Permlink | « Hide ]

Alexey Efimov - 10/Sep/03 09:54 AM

This is realy needed feature!
See also
http://jira.atlassian.com/secure/ViewIssue.jspa?key=JRA-2314

[ Permlink | « Hide ]

Uwe Goetzke - 25/Mar/04 03:32 AM

We have 15 master components and 170 subcomponents. In teh moment we prepend the subcomponent with the master component, but this is ugly

For example:

environment_JRun (Lead: Frank xyz) (Delete | Edit)
environment_Resin (Lead: Jens xyz) (Delete | Edit)
environment_configuration (Lead: Jens xyz) (Delete | Edit)
environment_customizing (Lead: Jens xyz) (Delete | Edit)
environment_help (Lead: Anita xyz) (Delete | Edit)
environment_licences (Lead: Alexander xyz) (Delete | Edit)
environment_setup (Lead: Jens xyz) (Delete | Edit)
environment_translations (Lead: Peter xyz) (Delete | Edit)
environment_unix (Lead: Frank xyz) (Delete | Edit)
environment_websphere (Lead: Frank xyz) (Delete | Edit)

so issues would be assigned only to subcomponents but you get a hierachical view for browsing.

[ Permlink | « Hide ]

Jeff Turner [Atlassian] - 21/Jun/04 12:04 AM

Breaking this up into multiple parts, so each can be tracked/voted for independently..

[ Permlink | « Hide ]

Martin Smyth - 14/Sep/04 08:22 AM

Does splitting an issue into multiple issues and then resolving it before any, let alone all, of the component issues have been resolved make sense? Has the sub-projects feature made it on to any roadmap yet?

[ Permlink | « Hide ]

Jeff Turner [Atlassian] - 15/Sep/04 08:09 PM

Martin,

> Does splitting an issue into multiple issues and then resolving it before any, let alone all, of the component issues have been resolved make sense?

When an issue can be broken down into independent issues, we prefer to do so (and mark the parent as closed), as the parts can then be debated and voted for separately.

> Has the sub-projects feature made it on to any roadmap yet?

Not for 3.0, although it will be up again for debate in 3.1.

[ Permlink | « Hide ]

L. Vermeulen - 15/Jan/08 03:39 AM

This issue is closed because it is duplicate, but he answer at the question is interresting. > Has the sub-projects feature made it on to any roadmap yet? Not for 3.0, although it will be up again for debate in 3.1.
We now at 3.12 and 4 is comming, is this feature still (allready 3 years) in debate!!!