Project

General

Profile

Actions

Feature #1917

closed

Required on close

Added by Felipe Campo over 15 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Custom fields
Target version:
-
Start date:
2008-09-18
Due date:
% Done:

0%

Estimated time:
Resolution:
Duplicate

Description

It would be useful to have a check item on issues related custom fields that force tha this field is mandatoty to fullfill when the issue change to a state registered for close.
It would be similar to the actual required field but only for the closure of the issue.


Related issues

Is duplicate of Redmine - Feature #703: Configurable required fields per tracker/status/roleClosedJean-Philippe Lang2008-02-21

Actions
Actions #1

Updated by Stephanie Collett over 15 years ago

+1 This would be great for requiring a field like 'resolution' on close.

Actions #2

Updated by Mikael Rudberg over 15 years ago

+1 for me too it would be even better if you could have a connection on all to state so for instance you could tell which fields where required for a particular state as in ClearQuest

e.g.

state : Assigned
field : Target Version : Required
field : Affected version : Optional
etc. etc.

Actions #3

Updated by Anonymous over 15 years ago

Stephanie Collett wrote:

+1 This would be great for requiring a field like 'resolution' on close.

I'm interested in this for the exact same thing. At the moment I have patched our system to have a hard-coded check for moving an issue to a closed state without the custom "resolution" field being set.

Actions #4

Updated by Jean-Philippe Lang over 15 years ago

  • Target version deleted (0.8)
Actions #5

Updated by Felipe Campo over 15 years ago

  • Assignee set to Jean-Philippe Lang

Jean-Philippe , the version erase means that the Feature was dismissed ??

Actions #6

Updated by Felipe Campo over 15 years ago

  • Assignee deleted (Jean-Philippe Lang)
Actions #7

Updated by Anonymous over 15 years ago

Felipe Campo wrote:

Jean-Philippe , the version erase means that the Feature was dismissed ??

I suspect it means that version 0.8 is being finalised, and that this feature has not yet been implemented so it won't be there. That doesn't mean that this will not be implemented in the future though - I'm watching this issue with anticipation personally. If I had more time I'd write a patch..... ahhhh, the memories of once having spare time are starting to come back to me :(

Actions #8

Updated by Jean-Philippe Lang over 15 years ago

Felipe, Nick is right.

Actions #9

Updated by Johan Levin almost 15 years ago

+1

Actions #10

Updated by Nicklas Holm almost 15 years ago

+1

Actions #11

Updated by Brian FInch over 14 years ago

+1

Actions #12

Updated by Steve Overton about 14 years ago

+1

Actions #13

Updated by Ryan Rangel over 12 years ago

I too need the ability to "require" a field to be filled in for the ticket to change state. Any chance we can get this feature?

Actions #14

Updated by Maxim Nikolaevich over 12 years ago

I too need the ability to "require" a field to be filled in for the ticket to change status
even #5686 created.

Actions #15

Updated by Mischa The Evil about 11 years ago

  • Subject changed from Requiered on close to Required on close
  • Status changed from New to Closed
  • Resolution set to Duplicate

This is superseeded by #703 (2.1.0). You can now configure required (and read-only) standard/custom fields per tracker, status and role.

Maxim, issue #5686 proposes something different than that what Felipe requested in this issue initially.

Actions

Also available in: Atom PDF