Content
View differences
Updated by Rob Guinness over 8 years ago
Steps to reproduce:
1\. Create a role with only the permission “Add work packages (also allows to add attachments to all work packages)”
2\. Assign that role to a user (create special test user, if necessary) in a specific project context.
3\. Sign in as that user.
4\. Try to access a page corresponding to adding a new work package, e.g. /projects/myproject/work\_packages/new
Expected behavior:
User should be able to access this page
Actual behavior:
Page returns with 403 status and message saying, “You are not authorized to access this page.” (see screenshot)
1\. Create a role with only the permission “Add work packages (also allows to add attachments to all work packages)”
2\. Assign that role to a user (create special test user, if necessary) in a specific project context.
3\. Sign in as that user.
4\. Try to access a page corresponding to adding a new work package, e.g. /projects/myproject/work\_packages/new
Expected behavior:
User should be able to access this page
Actual behavior:
Page returns with 403 status and message saying, “You are not authorized to access this page.” (see screenshot)