Feature #4670

Fine tune "New Issue"

Added by Jakob Meissner over 9 years ago. Updated over 2 years ago.

Status:ClosedStart date:2010-01-27
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues
Target version:-
Resolution:Duplicate

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

Related to Redmine - Feature #12005: Mightful workflow field enhancement: hide New
Related to Redmine - Feature #4485: Create an ACL privilege for assigning tickets New 2009-12-25
Duplicated by Redmine - Feature #9054: New Issue Submission Form Closed 2011-08-13
Duplicates Redmine - Feature #703: Configurable required fields per tracker/status/role Closed 2008-02-21

History

#1 Updated by Axel Kloss over 9 years ago

+1, really need this configurable or role-based (see also #1091)

#2 Updated by Axel Kloss over 9 years ago

and #703

#3 Updated by minkbear minkbear over 9 years ago

+1

#4 Updated by Bryce Ellis over 9 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.

#5 Updated by Dipan Mehta over 6 years ago

This is yet another duplicate of #703 + #12005

#6 Updated by Toshi MARUYAMA over 6 years ago

  • Category set to Issues

#7 Updated by Go MAEDA over 2 years ago

  • Duplicates Feature #703: Configurable required fields per tracker/status/role added

#8 Updated by Go MAEDA over 2 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.

Also available in: Atom PDF