Feature #4584

Require a Target Version and Category and provide a default version.

Added by Steve Overton almost 8 years ago. Updated 12 months ago.

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

0%

Category:Issues
Target version:-
Resolution:Fixed

Description

Currently, there is no support to require a target version and category to be entered on an issue. For all situations or projects this is not necessary but in our use and I assume others, these fields are required and there is no way to make them required. It would be nice to have a project setting to require one or both of these fields.

It would also be a nice feature to provide a default version when a new issue is created. This would have to be maintained on the project version.


Related issues

Related to Redmine - Feature #1828: Default target version for new issues Closed 2008-08-28
Related to Redmine - Feature #703: Configurable required fields per tracker/status/role Closed 2008-02-21

History

#1 Updated by Steve Overton about 7 years ago

+1 I have requests for this functionality.

#2 Updated by Brian Underwood almost 7 years ago

+1 as well. We require people (operationally) to enter a version for bugs (not for features), but I don't see a way to require this in Redmine

#3 Updated by Steven Wong about 5 years ago

+1

#4 Updated by Nan Cao almost 5 years ago

+1, to set Target version to Required and Providing a default value make it convenient and standard to create a issue.

#5 Updated by Dipan Mehta over 4 years ago

Requiring a target version and category is now achieved (at least post 2.0.x). Setting the Default Target value for new issue will be available under #1828.

Add related/duplicate #1828.

#6 Updated by Go MAEDA 12 months ago

  • Status changed from New to Closed
  • Resolution set to Fixed

Closing this issue because current versions of Redmine have these features.

  • Making target version and category mandatory: #703 (Redmine 2.1.0)
  • Default target version: #1828 (Redmine 3.2.0)

#7 Updated by Go MAEDA 12 months ago

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

Also available in: Atom PDF