Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-32814

Rework message in logs when permission and workflow conflict

    XMLWordPrintable

    Details

    • Type: Suggestion
    • Status: Gathering Interest (View Workflow)
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • UIS:
      28
    • Support reference count:
      16
    • Feedback Policy:
      We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      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

      1. Take any workflow where you can normally comment and add the following property to a status:
        jira.permission.comment.denied = denied
      2. 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

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              bberenberg Boris Berenberg (Inactive)
              Votes:
              135 Vote for this issue
              Watchers:
              86 Start watching this issue

                Dates

                Created:
                Updated: