New Roles cannot see Issue Statuses when updating issue.
Added by Ani G about 15 years ago
If I add new roles in the Administration menu, (say ProjectHead, ProjectLead etc), the users with those assigned roles cannot see the different Issue Statuses in the dropdown when updating an issue. The only status visible is New for these new roles. Even if I modify an existing role's name, say Manager to SrDeveloper, same bug.
I conducted various searches on the site for this, but didn't come up with anything. If anyone has a solution for this, it will be much appreciated.
Thanks.
Replies (4)
RE: New Roles cannot see Issue Statuses when updating issue. - Added by Ani G about 15 years ago
Forgot include my env info:
About your application's environment
Ruby version 1.8.7 (i686-linux)
RubyGems version 1.3.4
Rails version 2.1.2
Active Record version 2.1.2
Action Pack version 2.1.2
Active Resource version 2.1.2
Action Mailer version 2.1.2
Active Support version 2.1.2
Edge Rails revision unknown
Application root /home/ldiinter/public_html/projects
Environment development
Database adapter mysql
RE: New Roles cannot see Issue Statuses when updating issue. - Added by Mischa The Evil about 15 years ago
Check the FAQ?!?! You'll need to setup the workflow for the new roles properly most-likely ;-)
RE: New Roles cannot see Issue Statuses when updating issue. - Added by Ani G about 15 years ago
Thanks Misha.
That issue is about setting up a new status. However, it seems you have to activate all the statuses for every single issue type for any new role. This is insane. I liked Redmine. I do not any longer. Too many illogical workflows in its construction. Bah!
RE: New Roles cannot see Issue Statuses when updating issue. - Added by Mischa The Evil about 15 years ago
Ani G wrote:
[...] it seems you have to activate all the statuses for every single issue type for any new role [...]
Since Redmine 0.7 you are able to copy an existing workflow from another existing role, when you create new roles. For implementation-details and the related issue see #841.