Project

General

Profile

Workflow Settings Clarification

Added by Anonymous over 10 years ago

I've read through what little documentation I could find, as well as numerous bug reports and forum posts (such as #703 for example). However, I'm still a bit confused as to how the "Required" and "Read-only" fields apply to the fields for each status.

This is how I see this feature, although there is a good chance I'm simply misunderstanding it...

[New] status: "Description" = required "Priority" = read-only
[Open] status: "Description" = required "Priority" = required

In this simple example using only two fields, I would say the following rules should be true:

  • A new issue should only be saved with a [New] status if A "Description" has been set, while the "Priority" field should be shown but grayed out.
  • An issue should only be moved into [Open] once it has been confirmed, part of which involves specifying the priority of the task.

Am I simply doing something wrong here? Are there other rules that perhaps override these settings? I'm kinda stumped on this one, so any advice / suggestions would be greatly appreciated.

Currently I'm running Redmine 2.3.1.stable with the following plugins:

redmine_default_assign                   0.4
redmine_knowledgebase 3.0.0-devel1
redmine_landing_page 0.1.0
redmine_lightbox 0.0.1
redmine_people 0.1.6
redmine_redcarpet_formatter 2.0.1
redmine_track_control 1.0.8
status_button 0.1.0

Edit: I think I've managed to work out what was going wrong. The rules do seem to be applied as I thought, I failed to notice my user group though... Although the user I was testing with is in my "Software Dev" group, inside the current project this user was assigned to the "Lead" role. After editing "Lead" role rules, the changes were applying to my end user.

Still open to suggestions on how to best build up a system like this, to work it out myself may take a couple hours of trial and error testing.