Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
40
-
16
-
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Error in the logs:
2013-04-26 13:40:49,131 http-bio-8080-exec-5 INFO skim 820x795x1 1kyzuz0 127.0.0.1 /browse/KEY-1 [atlassian.jira.security.WorkflowBasedPermissionManager] comment not granted by 'denied' workflow permission
2013-04-26 13:40:49,131 http-bio-8080-exec-5 INFO skim 820x795x1 1kyzuz0 127.0.0.1 /browse/KEY-1 [atlassian.jira.security.WorkflowBasedPermissionManager] comment granted by permission scheme but DENIED by workflow
The following can also occur:
2013-09-03 08:49:14,148 http-bio-80-exec-21 INFO rca 529x20500x1 1iq6oj4 10.156.34.80 /browse/xxxx [atlassian.jira.security.WorkflowBasedPermissionManager] assign granted by permission scheme but DENIED by workflow
2013-09-03 08:49:14,164 http-bio-80-exec-21 INFO rca 529x20500x1 1iq6oj4 10.156.34.80 /browse/xxxx [atlassian.jira.security.WorkflowBasedPermissionManager] assign not granted by workflow perm granting assign to Gruppe 'jira-administrators'
Steps to reproduce
- Take any workflow where you can normally comment and add the following property to a status:
jira.permission.comment.denied = denied - Then visit an issue where this status applies. Check the logs and see the above message.
While this message definitely seems useful in theory, it is not really INFO level I think. Let's make it DEBUG level so that if debugging is enabled, the issue can be easily found.
Or remove the message entirely maybe
Attachments
Issue Links
- relates to
-
- Closed