Project

General

Profile

Actions

Feature #8050

closed

Mightful workflow field enhancement: visible, read only and mandatory

Added by Terence Mill over 13 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues workflow
Target version:
-
Start date:
2011-04-03
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

The problem with a bigger workflow is that some of the fields should be only visible at a later status (e.g. status=Test, which needs additional fields like "tester"), or the field should be set by a certain role only (field is readonly for other roles, e.g. progress is only used in development stage by developers) or a status can only be changed if a certain field is set (field is mandatory for status change and and role, e.g time estimatation must be set before status can change to planning)

I would propose a easy but mightful enhancement which will solve them all:

There should be a matrix to set rights, visibility and duty dependent on role and status
in every cell in the matrix there is a row for every field of tracker and every row has field name followed by 3 checkboxes:

  • visible (not visible)
  • read only (writable))
  • mandatory (optional writable)

Rules:

  1. if field is visible (visible=false then 2 and 3 are greyed)
  2. if field id read only (1 is true, read only=true then 3 is greyed)
  3. if field is mandatory ( 1 is true, 2 is false)

Since some users won't need this kind of advanced workflow there could be a default for this 3 properties for all fields.
Today the default is visible=true, read only=false and mandatory=false (Except Subject ;) )


Files

Screenshot0.jpg (23.1 KB) Screenshot0.jpg Terence Mill, 2011-05-18 15:56
Screenshot1.jpg (65.3 KB) Screenshot1.jpg Terence Mill, 2011-05-18 15:56
Screenshot2.jpg (344 KB) Screenshot2.jpg Terence Mill, 2011-05-18 15:56
workflow_permissions.png (13.7 KB) workflow_permissions.png Jean-Philippe Lang, 2012-07-15 18:26
NoRedStarForMandatoryField.png (49.2 KB) NoRedStarForMandatoryField.png Gurvan Le Dromaguet, 2012-09-03 16:05
workflow_hidden_field.diff (4.79 KB) workflow_hidden_field.diff Gurvan Le Dromaguet, 2012-09-28 12:29
workflow_hidden_field_v0.03.diff (8.73 KB) workflow_hidden_field_v0.03.diff Added possiblity to hide non-custom_fields Gurvan Le Dromaguet, 2012-10-02 11:27

Related issues

Related to Redmine - Feature #703: Configurable required fields per tracker/status/roleClosedJean-Philippe Lang2008-02-21

Actions
Related to Redmine - Patch #7444: Patch for improved issue edit permissionsClosedBrian Lindahl2011-01-25

Actions
Related to Redmine - Feature #2539: New project setting: mandatory/optional configuration for target version issue-attributeNew2009-01-19

Actions
Related to Redmine - Feature #9700: Allow to configure the visibility of the fields of the “New issue” form per roleClosed

Actions
Related to Redmine - Feature #9736: custom field visibility based on trackerClosed

Actions
Related to Redmine - Feature #3521: Permissions for roles to change fields per tracker/statusClosedJean-Philippe Lang2009-06-22

Actions
Related to Redmine - Feature #2500: configure custom fields as "required for status transition"Closed2009-01-13

Actions
Related to Redmine - Feature #12005: Mightful workflow field enhancement: hideNew

Actions
Related to Redmine - Feature #393: Role that can't assign a ticketClosed

Actions
Related to Redmine - Feature #4707: private fieldsNew2010-02-01

Actions
Related to Redmine - Feature #8313: Restrict Assignee List by RoleNew2011-05-06

Actions
Related to Redmine - Feature #10162: require notes on specific fields getting set to specific valuesNew

Actions
Has duplicate Redmine - Feature #11329: Private custom fieldsClosed

Actions
Actions

Also available in: Atom PDF