ChiliProject is not maintained anymore. Please be advised that there will be no more updates.

We do not recommend that you setup new ChiliProject instances and we urge all existing users to migrate their data to a maintained system, e.g. Redmine. We will provide a migration script later. In the meantime, you can use the instructions by Christian Daehn.

Release (Feature #1266)

Added by Johannes Dohmen at 2013-05-13 03:29 pm. Updated at 2013-05-13 03:29 pm.

Status:Open Start date:2013-05-13
Priority:Normal Due date:
Assignee:- % Done:

0%
Category:-
Target version:-
Remote issue URL: Affected version:

Description

I want to suggest a Release feature.

With Release I denote a mapping from a name to a set of projects with a specific version. For example lets assume chiliproject instance has three projects:
p1, p2 and p3
with versions:
p1_v1, p1_v2, p2_v1, p2_v2 and p3_v1.

A Release might be named R1 and consist of project p1 with version p1_v1 and project p2 with version p2_v1.
Another (subsequent) Release might be named R2 and consists of project p1 with version p1_v2 and project p2 with version p2_v1 and p3 with version p3_v1.

Needed features:
  • Create a new Release (with at least its name)
    It would for subsequent releases be of great advantage to be able to copy from a previous one.
  • Assign projects to a Release
    A Release should be able consist of an arbitrary number of projects. Each project must be assigned with exactly one of its own configured versions.
  • Query a Release
    It should be possible to query a release (instead of a project). For example it should be possible to get a list of all open bugs of R1
  • Advanced features
    More advanced features like having a roadmap for a feature would be nice ;-)

History

Also available in: Atom PDF