Redmine

It was already discussed before but I can't find where.
In order not to break the workflow, a solution would be to give to admin users all the status transitions given to any role.

• 3 statuses are defined: A, B, C
• 2 roles: R1, R2
• R1 is allowed to do A -> B
• R2 is allowed to do B -> C

=> admins are allowed to do A -> B and B -> C (but not B -> A or C -> A and so on)

What do you think?

I really like it the way it is. The admin can change his/her role within the project as he/she see fit.

I use that all the time to be able to test different workflows. Imagine trying to create a workflow and having to log on as a different user all the time while testing.

My vote is for keeping this as it is.

/T

Hi, Thomas
I think that the admin user's duty is to offer help to other users who may not be familiar to redmine. The admin user is a assistant of other users. He is commonly not a member of projects(at least he is not the member of every project).
So I think that allowing admin user to change issue's status of every project is a good feature.

But your request to keep the way as now is reasonable, too. Maybe we should wait for more comments.

By the way, after I studied the code about issue' status, I found that it was not very easy to implement this feature as I have expected. ^_

IMO, Administrator == root user and should have full access to everything. If you want to test workflows, you should have to change to a different user. That is how every other system I've used works.

Throwing in my thoughts, I agree that it should be changed. Every other aspect about an issue can be changed by the admin, including the person it is assigned to, the tracker, the project, etc. It can even be deleted. But the status cannot be changed... that seems out of place, especially considering that the admin is not prevented in any way from applying the workaround of temporarily adding the project to his/her account.

Jean-Philippe Lang wrote:

It was already discussed before but I can't find where.
In order not to break the workflow, a solution would be to give to admin users all the status transitions given to any role.

Example:

• 3 statuses are defined: A, B, C
• 2 roles: R1, R2
• R1 is allowed to do A -> B
• R2 is allowed to do B -> C

=> admins are allowed to do A -> B and B -> C (but not B -> A or C -> A and so on)

What do you think?

I vote to allow the admin to break the workflow. Perhaps a dialog box could ask "Are you sure?", or maybe have a warning next to the offending selections in the list, or even a warning (think red validation) that says it could break the workflow. Another thought... there could be a checkbox in workflow settings that says "[ ] Administrators are subject to workflow restrictions".

Anyway, there may be a good reason to break it... say that some issues have been left unresolved for a long time, and an admin needs to do a bulk close on the list.

And here's another aspect of your scenario to think about: could the admin also do A -> C now, since he/she can do A -> B -> C?

(By the way... great job on Redmine in general... the improvements over time have been much appreciated!)

It is very easy to create a super-user-role that have a checkmark in every box and thus can change anything.

Easy to add myself to the superuser-role if needed. Usually i don't use it.

Anyway, there may be a good reason to break it... say that some issues have been left unresolved for a long time, and an admin needs to do a bulk close on the list.

That excactly is the situation I face very often. And based on the nature of our business we have hundreds of projects where I would have to assign myself in a super-admin role.

So I definitly would like to do any status transition as admin.