Stanislav N.
opened 3 years ago
-
Each value of a enum type field has applicable projects. With this, the same issue field can be configured to have different enum values for different projects.
-
This can be a problem when e.g. Type field will contain more and more values. I think even 50 values already will be a visual problem at least - it will be hard to navigate around them in admin panel and "compiling" list of values in the head for every project will be a pain.
-
Using display name has its own problem, for instance, if you have two fields using same display name, how to tell which field is being queried against if user queries against the display name?
OneDev tries to make simple things easy, and complicated things possible. In case of different projects using different enum values, I think this is not very common for a self-hosted instance. Note that you do not need to specify each applicable project for a particular enum value, you may specify a path pattern instead.
-
Previous Value Current Value Open
Closed
| Type |
Improvement
|
| Priority |
Normal
|
| Assignee |
(I'm on version 7.9.7)
I have two projects, one has issue types "Bug", "Feature request", "Discussion", second - "Helpdesk", "Task", "Marketing". Currently there is no possibility to have two "Type" enumerations for two different projects as field name should be unique, so I've created two enumerations -
[project1] Typeand[project2] Type.For ease of use and eye-candy I want to request to implement "display name" for fields, so names could have something to distinguish between projects and be uique, yet in issues display name is shown which can be reused as many times as needed, so
[project1] Typeand[project2] Typefields could have same nameTypeshown in issues.