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

Cannot add comment in transition screen if destination status has jira.permission.comment.user set to false

XMLWordPrintable

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      This seems to be caused by the bugfix for: https://jira.atlassian.com/browse/JRA-40310

      In 6.3.9 and later, you can no longer add a comment in a transition screen if the destination status has jira.permission.comment.user set to false or denied. The message below is displayed in a red banner when you try to transition the issue:
      <username>, you do not have the permission to comment on this issue.

      This should not be the case because the comment permission property should be based on the CURRENT status of the issue. To put it in simply, the transition was not yet executed so adding a comment should be allowed.

          Form Name

            [JRASERVER-40997] Cannot add comment in transition screen if destination status has jira.permission.comment.user set to false

            Sean Bennett added a comment -

            I'm on 6.3.14 in Live and it doesnt work whereas my test environment is 6.4.13 and it does!

            Sean Bennett added a comment - I'm on 6.3.14 in Live and it doesnt work whereas my test environment is 6.4.13 and it does!

            Hrant added a comment - - edited

            Thanks Oswaldo,

            Hrant added a comment - - edited Thanks Oswaldo,

            Oswaldo Hernandez (Inactive) added a comment -

            Hi hrant933786460,

            Please see my reply at JRA-44123. The scope of this fix was the jira.permission.comment.user property.

            Regards,

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

            Oswaldo Hernandez (Inactive) added a comment - Hi hrant933786460 , Please see my reply at JRA-44123 . The scope of this fix was the jira.permission.comment.user 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 -

            Hi jochen.kypke@emmos.de,

            Unfortunately no, the JIRA Bugfix team only works on the current stable maintenance line for JIRA which at the moment is the JIRA 7.0.x series.

            Consequently, you will need to upgrade to JIRA 7.0.3 (as soon as it is available) or later to obtain this fix. If you need help with your upgrade, you can raise a support request with us at https://support.atlassian.com and we will be happy to assist you with this process.

            Regards,

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

            Oswaldo Hernandez (Inactive) added a comment - Hi jochen.kypke@emmos.de , Unfortunately no, the JIRA Bugfix team only works on the current stable maintenance line for JIRA which at the moment is the JIRA 7.0.x series. Consequently, you will need to upgrade to JIRA 7.0.3 (as soon as it is available) or later to obtain this fix. If you need help with your upgrade, you can raise a support request with us at https://support.atlassian.com and we will be happy to assist you with this process. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            JK added a comment -

            Could you please provide a fix for Jira 6, too? There may be only a few projects affected, but within these this parameters are fully unusable.

            JK added a comment - Could you please provide a fix for Jira 6, too? There may be only a few projects affected, but within these this parameters are fully unusable.

            Oswaldo Hernandez (Inactive) added a comment -

            Hi obiettivolavoro,

            We will release this fix as part of JIRA Server 7.0.3.

            The fix implemented will allow the user to add the comment during the transition if either the original or or the destination status allow for the comment to be added.

            Regards,

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

            Oswaldo Hernandez (Inactive) added a comment - Hi obiettivolavoro , We will release this fix as part of JIRA Server 7.0.3. The fix implemented will allow the user to add the comment during the transition if either the original or or the destination status allow for the comment to be added. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            ITCS Obiettivo Lavoro added a comment -

            i will suggest developers to think about the possibility to build a parameter in jira to decide how to process the permission check ( at the beginnig for some customers or in the enc for others). This could fix the problem for everyone.

            ITCS Obiettivo Lavoro added a comment - i will suggest developers to think about the possibility to build a parameter in jira to decide how to process the permission check ( at the beginnig for some customers or in the enc for others). This could fix the problem for everyone.

            Oswaldo Hernandez (Inactive) added a comment -

            Should be fixed together with JRA-44123

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

            Patrice Foerster added a comment -

            Even if Add a comment to an issue if one is entered during a transition. is the first post function, I am getting the same error message
            Patrice Förster, you do not have the permission to comment on this issue.

            1. Add a comment to an issue if one is entered during a transition.
            2. Set issue status to the linked status of the destination workflow step.
            3. Assign the issue to the reporter.
            4. Update change history for an issue and store the issue in the database.
            5. Re-index an issue to keep indexes in sync with the database.
            6. Fire a Issue Closed event that can be processed by the listeners.

            Patrice Foerster added a comment - Even if Add a comment to an issue if one is entered during a transition. is the first post function, I am getting the same error message Patrice Förster, you do not have the permission to comment on this issue. Add a comment to an issue if one is entered during a transition. Set issue status to the linked status of the destination workflow step. Assign the issue to the reporter. Update change history for an issue and store the issue in the database. Re-index an issue to keep indexes in sync with the database. Fire a Issue Closed event that can be processed by the listeners.

              ohernandez@atlassian.com Oswaldo Hernandez (Inactive)
              dleng Daniel Leng (Inactive)
              Affected customers:
              30 This affects my team
              Watchers:
              46 Start watching this issue

                Created:
                Updated:
                Resolved: