Defect #28205

Wrong values in status combo

Added by Albrecht Dreß almost 5 years ago. Updated over 4 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:


Category:Issues workflow
Target version:-
Resolution: Affected version:3.3.1


I would like to have the following configuration for the workflow of a Reporter:

  1. [s]he may only create or re-open a closed ticket;
  2. if a ticket is in state ”Feedback”, [s]he may edit the ticket, and the next state must be In Progress.

So I gave the Reporter Role the issue tracking permissions (inter alia) “Edit issues” and “Add notes”, and configured the workflow as in the attached screenshot “Config.png”.

However, when a user with role Reporter now edits a ticket in state ”Feedback” for which [s]he is the assignee, the combo for “Status” (see screenshot “Result.png”) shows both the “required” next state (In Progress) and the current state (Feedback) as possible values. But the latter should actually not be allowed according to the configuration.

Did I miss something in the configuration, or is this a bug (or feature)?

My environment, on a standard Debian Stable (Stretch) box:
  • Redmine version: 3.3.1.stable
  • Ruby version: 2.3.3-p222 (2016-11-21) [x86_64-linux-gnu]
  • Rails version:
  • Environment: production
  • Database adapter: PostgreSQL

Config.png - Workflow configuration (49.1 KB) Albrecht Dreß, 2018-02-17 15:25

Result.png - Resulting Status options (9.52 KB) Albrecht Dreß, 2018-02-17 15:25


#1 Updated by Robert Paulsen over 4 years ago

I'm poking around trying to see if there is a bug reported for my issue, which is this: Existing tasks do not reflect changes to workflow. If I create a task, then change the workflow, the status combo doesn't reflect the correct value. But if I create a new task it does.

This might be why you're not seeing what you're expecting.

Also available in: Atom PDF