Feature #685
New Custom Field "Found in Version"
| Status: | New | Start: | 2008-02-18 | |
| Priority: | Normal | Due date: | ||
| Assigned to: | Jean-Philippe Lang | % Done: | 0% |
|
| Category: | Tickets | |||
| Target version: | - | |||
| Resolution: |
Description
Hi,
I think it would be great to have a custom field "Found in Version"
which contains a drop down Box with the versions like in "Fixed version".
The point is that our Testers create defect Tickets and they
should be able to choose the version in which the defect occured.
This would then be the field "Found in Version".
The developers look at the ticket a write down their comment
and estimated effort.
The managers decide in which version this should be fixed with "Fixed Version" Field.
This also appears in the roadmap then (as it is done now).
Reversly you would be able to see how many defects occured in an already
finished version with the "Found in Version" Field.
History
2008-02-19 09:27 - Thomas Lecavelier
Hi Sven,
As you said it, it would be a custom field. Custom fields can be created by your redmine administrator. But maybe I hadn't understand your point?
2008-02-19 09:33 - Sven Schuchmann
Your are right, this would be a custom field.
But the custom field should be a drop down list
with a all versions of the current project
(like "Fixed version").
At this time I am only able to create a custom field of
type "list" and enter all versions by Hand.
2008-02-20 10:49 - Thomas Lecavelier
Ok, so the feature request is more a "add project based data sources for custom field", like Version, affected users and so on... Maybe could we enumerate here all datas that should feed a list in a custom field?
2008-02-21 09:34 - Sven Schuchmann
In my opinion that would only be two:
- Versions in a project
- Users assigned to a project
Or am I missing some?
2008-05-19 17:40 - Thomas Lecavelier
- Target version deleted (
0.8)
Reset "target version" field.
It's not the proper way to get a feature implemented...
2008-05-24 07:57 - Bram Verburg
This one is important for me too, since I know this will be a show-stopper for replacing Bugzilla with Redmine in my organization. I started working on a patch and I could use some input.
I added the following custom field types: users, projects, sub-projects, versions and members. I also added a mechanism to limit types to certain places (e.g. sub-projects, versions and members only work in the context of issues and projects, so they shouldn't be available as a custom field for users).
The problem with projects (and sub-projects) is that projects may be private, and therefore different users will see different lists. Should I drop these two field types, or would be it acceptable to show a list that includes private projects to all users?