Defect #11625

Administrator Does Not Follow Workflow For Project

Added by William Roush over 8 years ago. Updated over 8 years ago.

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

0%

Category:Permissions and roles
Target version:-
Resolution:Invalid Affected version:1.4.0

Description

Alright fairly simple, I have a few roles:

  • Manager
  • Developer
  • Technician

Developers have additional workflow:
"Pending QA Deployment" > "Deployed to QA" > "Passed QA", available for the "Developer" and "Manager" roles.

Technician have the default workflow.

For some reason while logged in as an Admin on a project I'm given Technician access to, I am given the developer workflow!

This is a bit odd, anyone got ideas?

Tech_Bug_1.PNG (60.5 KB) William Roush, 2012-08-13 15:54

Tech_Bug_2.PNG (43.5 KB) William Roush, 2012-08-13 15:54


Related issues

Duplicated by Redmine - Defect #22162: Workflow - Tracker/Role is not "project" specific Closed

History

#1 Updated by Jean-Philippe Lang over 8 years ago

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

I'm closing it because administrators can apply any status transition given to any role, by design. See #2323.

#2 Updated by William Roush over 8 years ago

Jean-Philippe Lang wrote:

I'm closing it because administrators can apply any status transition given to any role, by design. See #2323.

But what about projects where that workflow is invalid? No one in that project has that workflow, so no one can transition a ticket set to "Pending QA Deployment", which is kind of a workaround for #1853.

#3 Updated by William Roush over 8 years ago

However, I still cannot go from "New" to "Deployed to QA" or "Passed QA" as those are globally invalid transitions, so neither are all options available.

#4 Updated by Toshi MARUYAMA almost 5 years ago

  • Duplicated by Defect #22162: Workflow - Tracker/Role is not "project" specific added

Also available in: Atom PDF