Feature #2500

configure custom fields as "required for status transition"

Added by Olivier Abad almost 9 years ago. Updated almost 5 years ago.

Status:ClosedStart date:2009-01-13
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues workflow
Target version:-
Resolution:Duplicate

Description

I would like to be able to configure custom fields as "required" but only for some issue statuses.

For example, in our workflow, we defined a status named "Livré", and a custom field named "Réf dossier livraison", and we would like this field to be filled when changing the ticket status to "Livré" but not before.

dynamic-mandatory-issue-field.js - Javascript for theme to check custom fields in transition. (1.36 KB) Sébastien Gripon, 2011-11-02 18:13


Related issues

Related to Redmine - Feature #8050: Mightful workflow field enhancement: visible, read only ... Closed 2011-04-03
Duplicated by Redmine - Feature #8005: Required fields depending on status Closed 2011-03-28
Duplicated by Redmine - Feature #9280: Required Custom field on Status Closed 2011-09-19
Duplicates Redmine - Feature #703: Configurable required fields per tracker/status/role Closed 2008-02-21

History

#1 Updated by Hans Kazan over 8 years ago

+1

#2 Updated by Steve Overton about 7 years ago

I believe this would be a major change to Redmine but it would take it to the next level. We are currently using ClearQuest (contractual) and Redmine and one of the few things (that matter to us) that ClearQuest has that Redmine does not is to have required fields per status.

+1

#3 Updated by Torgrim Brochmann almost 7 years ago

+1

Required per status for all fields, not just custom fields

#4 Updated by Etienne Massip almost 7 years ago

  • Category changed from Issues to Issues workflow

#5 Updated by Terence Mill almost 7 years ago

+1
This is very essential for use, but we already live this feature by process doc and this isn't very safe. A redmine enforced behavour would be much better.

#6 Updated by Gilles DUGAST almost 7 years ago

+1
Very essential feature! I'd like to see it very soon.

#7 Updated by Fabrice MOUCHERE almost 7 years ago

+1

#8 Updated by Julio Blanco over 6 years ago

+1 Critical feature

#9 Updated by Bruno Samora over 6 years ago

+1

#10 Updated by Andrea Saccavini over 6 years ago

+1

#11 Updated by Paulo Oliveira over 6 years ago

+1

#12 Updated by Jason Waldrip over 6 years ago

+1

#13 Updated by Clyde Goffe over 6 years ago

+1

#14 Updated by Gurvan Le Dromaguet over 6 years ago

+1 Almost mandatory, key feature to have reliable information when >100 users

#15 Updated by Sébastien Gripon about 6 years ago

+1

#16 Updated by Daniel Moore about 6 years ago

Sébastien Gripon wrote:

+1

+1

#17 Updated by Daniel Moore about 6 years ago

+1

#18 Updated by Sébastien Gripon about 6 years ago

Note that in order to get this important feature, we have inserted javascript function that check some fields when changing the status. This is really easy to implement but should be built in redmine.

#19 Updated by Gurvan Le Dromaguet about 6 years ago

Sébastien Gripon wrote:

Note that in order to get this important feature, we have inserted javascript function that check some fields when changing the status. This is really easy to implement but should be built in redmine.

Hi Sébastien,
In case your code is re-usable, any chance to share it with us ?

#20 Updated by Sébastien Gripon about 6 years ago

The code was not really reusable because of many business specific rules. However, I attached a clean dirty version with no warranty! Not tested, with no support! Sorry but time is missing ;o)

#21 Updated by Gurvan Le Dromaguet about 6 years ago

Thanks Sebastien,
I should have time to take a look at it and test it on my generic environment tomorrow.
will come back thereafter :)

#22 Updated by Terence Mill about 6 years ago

This is covered by #8050

#23 Updated by Jean-Philippe Lang over 5 years ago

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

Implemented as part of #703.

Also available in: Atom PDF