Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-44123

Comment in transaction screen blocked by JIRA Workflow Step Property jira.permission.comment.denied

XMLWordPrintable

      Steps to replicate:

      1. I have 2 statuses - "In Progress" and "Resolved".
      2. I've set jira.permission.comment.denied property on status "Resolved".
      3. When I try fire "Resolve" on issue, I see transaction screen with "Comment" field.
      4. If I leave "Comment" field is blank, the transaction will be successful
      5. But if I type some text in the "Comment" field, the transaction fails and I get an error "username, you do not have the permission to comment on this issue."

      I suppose it is due to the don't correct order of the transaction. Initially task is entering in a new status with the established properties, and then are set the field values, such as "Comment"

            [JRASERVER-44123] Comment in transaction screen blocked by JIRA Workflow Step Property jira.permission.comment.denied

            Hrant added a comment -

            Thanks Oswaldo, logged a support ticket, I surely hope that it gets it due attention instead of falling in a backlog.
            It behooves us as why an engineer would fix this just for 

            jira.permission.comment.denied

            instead of seeing the bigger picture and realizing that this limitation applies to 

            jira.permission.*

            Hrant added a comment - Thanks Oswaldo, logged a support ticket, I surely hope that it gets it due attention instead of falling in a backlog. It behooves us as why an engineer would fix this just for jira.permission.comment.denied instead of seeing the bigger picture and realizing that this limitation applies to jira.permission.*

            Oswaldo Hernandez (Inactive) added a comment -

            HI hrant933786460,

            As per the issue's description, the scope of this fix was the jira.permission.comment.denied property.

            Consequently, could you please raise a support case with us at https://support.atlassian.com so one of our support engineers can assist you in raising a bug for the jira.permission.work Once that is done, we will triage it an assess the possibility of doing a fix for that property.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - HI hrant933786460 , As per the issue's description, the scope of this fix was the jira.permission.comment.denied property. Consequently, could you please raise a support case with us at https://support.atlassian.com so one of our support engineers can assist you in raising a bug for the jira.permission.work Once that is done, we will triage it an assess the possibility of doing a fix for that property. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            Hrant added a comment -

            Is this truly fixed? and if so it is only fixed for
            jira.permission.comment ?
            Why not fix it for jira.permission.*
            We have the same problem with jira.permission.work
            We set the step to allow or not allow "Work Logging"
            The transition steps include "Work Log"
            It appears that the transition is executed before work log is committed hence causing the failures

            Can you please confirm if this is fixed?
            We are running cloud Jira version 7.2.0-OD-03-014

            Thanks

            Hrant added a comment - Is this truly fixed? and if so it is only fixed for jira.permission.comment ? Why not fix it for jira.permission.* We have the same problem with jira.permission.work We set the step to allow or not allow "Work Logging" The transition steps include "Work Log" It appears that the transition is executed before work log is committed hence causing the failures Can you please confirm if this is fixed? We are running cloud Jira version 7.2.0-OD-03-014 Thanks

            Oswaldo Hernandez (Inactive) added a comment -

            Should be fixed together with JRA-40997

            Oswaldo Hernandez (Inactive) added a comment - Should be fixed together with JRA-40997

              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              a6d83f826dab Andrey Ivanov
              Affected customers:
              4 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: