Feature #21149

Linking "Possible values" for List custom fields to another custom fields of same type.

Added by VD DV about 2 years ago. Updated 10 months ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Custom fields
Target version:-
Resolution:

Description

Hi,
I hope that this feature is not too complex to implement, and other redmine users should find it useful.

To point to idea of extending Redmine with this feature, I have to explain the use case first.

We have multiple (almost hundered) projects that share same settings regarding custom fields, roles, ... Those projects have defined complex workflow, that limits users to change some Custom fields. As you know tweaking workflow is tricky bussines, so we prefer that all projects share same set of custom fields.
Right now we have to track define new custom field that will be reference to contract with customer. Each project should have list of their own contract numbers. One of solutions is to use Category field, but that field is already used for another purpose.
I think that it will be very useful to implement following solution:
In the phase of creating New Custom Field (List type), it would be nice to have two options for "Possible values":
- Static list of Possible values (1)
- Linked list of Possible values (2)
Those options should not be mutually exclusive. Effective list of possible values is formed as distinct union of Static and Linked list of Possible values.

First (1) one already exists.
Second (2) should have link to another Custom Field of the same type, but on another entity (Issues, Spent Time and Projects).

First example:
If creating Custom field of type List for Issues or Spent Time, it would be nice to link to possible values of Custom field (type list) at Owning Project level.

Another example:
If creating Custom field of type List for Projects, it would be nice to link to possible values of Custom field (type list) at Parent Project level.

In this way our problem with contract numbers will be solved in the way that each Project have custom field (type list) with valid Contract numbers for that project. Let's name it Projects_Contract_IDs.
Issues will have Custom field (type list) named for example Issue_Contract_ID. That Issue_Contract_ID links values to Project level Custom field named Projects_Contract_IDs.
With this feature, we can manage more similar projects very flexible, simply by changing values for custom fields on Project level.
Custom fields on Subproject level, Issue level and Timelog level simply inherits values from Custom fields from Project level.

Thank you


Related issues

Related to Redmine - Feature #21060: Custom field format with possible values stored as records Closed
Related to Redmine - Feature #21568: Adding support of logic relationship between boolean cust... New
Related to Redmine - Feature #25043: Custom fields (type List): values inheritance, per projec... New

History

#1 Updated by Toshi MARUYAMA about 2 years ago

  • Related to Feature #21060: Custom field format with possible values stored as records added

#2 Updated by VD DV almost 2 years ago

Is there any option to put this issue at "Candidate for next major release" category?
It would be great enhancement for Redmine.
Hope it is not so difficult to implement compared to benefits that this feature brings to Redmine.

#3 Updated by Toshi MARUYAMA almost 2 years ago

  • Related to Feature #21568: Adding support of logic relationship between boolean custom field values and other custom field added

#4 Updated by VD DV over 1 year ago

Is there possibility to put this issue as "Candidate for next major release" in near future?
If you need some clarification on this feature, do not hesitate to ask.

#5 Updated by VD DV 10 months ago

This issue relates #25043

Looking forward for this feature!

#6 Updated by Toshi MARUYAMA 9 months ago

  • Related to Feature #25043: Custom fields (type List): values inheritance, per project values added

Also available in: Atom PDF