Feature #6716

Linking version to category

Added by Stefano Lenzi about 7 years ago. Updated about 7 years ago.

Status:NewStart date:2010-10-21
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:-
Resolution:

Description

Use Case

The Galaxy company is developing a new project called Solar System foo project base on several components: Earth, Mercury, Jupiter, and others. The Galaxy administrator decided to define a category for each components in Redmine.
During the project life cycle components Earth reached versions: 1.0.0, 0.8.0, 0.6.0 The component Mercury reached versions 1.2.0, and 1.0.0
Andrea, a developer, find an issue on Mercury component, so she decides to create an issue on Redmine. During the compilation of the "new issue" form she select first the Mercury category from the drop-down menu and later she select version 1.2.0 from the drop down list that shows only 1.2.0 and 1.0.0 (none of the versions related to other components are proposed)

Specific Solution

Allow the administrator to create a relationship between version and category from the administration of the version, so that after the selection of a category in the forum Redmine can change the content of version field by means of AJAX

General Solution

Allow the administrator to create a link between two fields along with a filtering function. For example if the start with function is defined and the administrator creates a link between category and version, she defines the name of the version as <category>-<version>, then the user select a category the filter "start with" is used by AJAX to filter out version that do not starts with selected category.


Related issues

Related to Redmine - Feature #6717: Custom list field with dynamic list content New 2010-10-21

History

#1 Updated by Terence Mill about 7 years ago

Its kind related to sharepoint lists. I really like the idea oc easy creating relational tables/list idea which relate to each other and can be filtered this way. You shallfirst provide an plugin independent to internal objects (e.g tickets ) and later try to ehance fields of linked lists to tickets.

Also available in: Atom PDF