Redmine

The fix for this is very small (I think), I will dig it up from my home Redmine install. I am too insecure about Rails development, though, so I am reluctant to submit this as an actual patch without someone proofreading it.

Actually statuses that are not allowed are displayed but you cannot select them. Why do you want to completely hide them ? Do you have an explicit example ?

It can be confusing for users when you have multiple workflows with numerous custom issue statuses, to see statuses that issues in the current tracker could never have. Having to skip over statuses when changing them can be tedious - we have a tracker with very "small" issues, that require being edited in Bulk, and advanced from one status to the next. Having to skip over a large block of unselectable statuses to "done" or "closed", which needs to be at the bottom of the list to be intuitive, seems to defeat the slick elegance of the context menu.

The unused statuses also take up screen real-estate in this very small menu. The menu gets very large when all the unused statuses are always listed; it often touches or overlaps the screen or window borders.

Last, but not least, the "Status" field in "Edit Issue" itself does only list valid statuses for each issue - so it's a question of consistency, too. Same goes for the workflow definition pane in the administration menu - filtering there is even on by default.

Addendum:

Jean-Baptiste Barth wrote:

Actually statuses that are not allowed are displayed but you cannot select them. Why do you want to completely hide them ? Do you have an explicit example ?

Why would you want to show them? Do you have an explicit example ?

(sorry for the retort, but when is it sensible to actually show a status that an issue can never, ever obtain?)

Maybe I misunderstood the problem you pointed out : I though you were talking about statuses the user cannot apply because of a workflow limitation. If we hide statuses unreachable by the current user, we should also change all other fields display in context menu, it's a more general problem. Your proposed patch hide some statuses an issue can have, but that the current user cannot set himself.

If you confirm we should only hide statuses that nobody can reach, then OK, I 100% agree and I'll take a look at it.

Yes, I mean only statuses that the tracker never uses, and grey out statuses the user can't set it to.

In my case, it didn't occur to me that my patch took all the disallowed issues out - the one for 0.9.x didn't so maybe I screwed something up. I will look into it a little, too.