Feature #4670
closed
Fine tune "New Issue"
0%
Description
Why can anybody (=any role) assign a due date, etimated time, %done, assigned to, or target version for an new issue? This makes sense only for the developers themselves and is unintersting (best) or confusing (worse) for the bug/feature reporters.
As it seems, even redmine has problems with this, as you put these 2 lines in "SubmittingBugs":- please DON'T fill the target version field: let the developers decide when integrate
- please DON'T assign the feature request to anybody, let the developers deal with it
It is possible already to add custuom fields, so why not making the default fields deletable?
best regards,
jakob
Related issues
Updated by Axel Kloss almost 15 years ago
+1, really need this configurable or role-based (see also #1091)
Updated by
Updated by Bryce Ellis over 14 years ago
I am very happy to have finally found a tool that ties together the vital parts of project(s) management as well as redmine does. Great Job! I am in the process of standing up a version with many external contributers and a need to manage the content of incremental baselines. Due to the number and diversity of contributers on our project, the features of and changes to a target version must be tightly controlled by a configuration control board. This issue means that the board must extend extra effort to guard against any redirection of issues.
Updated by Dipan Mehta almost 12 years ago
Updated by Toshi MARUYAMA
Updated by Go MAEDA almost 8 years ago
- Is duplicate of Feature #703: Configurable required fields per tracker/status/role added
Updated by Go MAEDA almost 8 years ago
- Status changed from New to Closed
- Resolution set to Duplicate
Implemented by #703 (Redmine 2.1.0).
Administrators can make fields read only / required in workflow page.