Project

General

Profile

Actions

Feature #2500

closed

configure custom fields as "required for status transition"

Feature #2500: configure custom fields as "required for status transition"

Added by Olivier Abad almost 18 years ago. Updated over 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
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.


Files

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

Related issues 4 (0 open — 4 closed)

Related to Redmine - Feature #8050: Mightful workflow field enhancement: visible, read only and mandatory ClosedActions
Has duplicate Redmine - Feature #8005: Required fields depending on statusClosedActions
Has duplicate Redmine - Feature #9280: Required Custom field on StatusClosedActions
Is duplicate of Redmine - Feature #703: Configurable required fields per tracker/status/roleClosedJean-Philippe LangActions

Updated by Hans Kazan over 17 years ago Actions #1

+1

Updated by Steve Overton about 16 years ago Actions #2

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

Updated by Torgrim Brochmann over 15 years ago Actions #3

+1

Required per status for all fields, not just custom fields

Updated by Etienne Massip over 15 years ago Actions #4

  • Category changed from Issues to Issues workflow

Updated by Terence Mill over 15 years ago Actions #5

+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.

Updated by Gilles DUGAST over 15 years ago Actions #6

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

Updated by Fabrice MOUCHERE over 15 years ago Actions #7

+1

Updated by Julio Blanco over 15 years ago Actions #8

+1 Critical feature

Updated by Bruno Samora over 15 years ago Actions #9

+1

Updated by Andrea Saccavini over 15 years ago Actions #10

+1

Updated by Paulo Oliveira over 15 years ago Actions #11

+1

Updated by Jason Waldrip over 15 years ago Actions #12

+1

Updated by Clyde Goffe over 15 years ago Actions #13

+1

Updated by Gurvan Le Dromaguet about 15 years ago Actions #14

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

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

+1

Updated by Daniel Moore about 15 years ago Actions #16

Sébastien Gripon wrote:

+1

+1

Updated by Daniel Moore about 15 years ago Actions #17

+1

Updated by Sébastien Gripon about 15 years ago Actions #18

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.

Updated by Gurvan Le Dromaguet about 15 years ago Actions #19

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 ?

Updated by Sébastien Gripon about 15 years ago Actions #20

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)

Updated by Gurvan Le Dromaguet about 15 years ago Actions #21

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

Updated by Terence Mill about 15 years ago Actions #22

This is covered by #8050

Updated by Jean-Philippe Lang over 14 years ago Actions #23

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

Implemented as part of #703.

Actions

Also available in: PDF Atom