-
Bug
-
Resolution: Fixed
-
Medium
-
6.3.9, 6.4, 6.5-OD-07
-
6.03
-
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.
- is caused by
-
JRASERVER-40629 Default post functions order causing values added in transition to be denied with certain status' property
- Gathering Impact
- is duplicated by
-
JRACLOUD-65844 With jira.permission.comment.user = denied, comments field still appears on resolve screen
- Closed
-
JRASERVER-41017 Workflow step which contain property to restrict comment is blocking transition with comment before status changed
- Closed
- is related to
-
JRASERVER-40310 Changing assignees in transition screen is taking into account the permission property of the CURRENT status, not the DESTINATION status
- Closed
- relates to
-
JRACLOUD-40997 Cannot add comment in transition screen if destination status has jira.permission.comment.user set to false
- Closed
-
JRASERVER-32715 jira.permission.comment property in workflow step causing users to be unable to transition or view issues
- Closed
-
JRASERVER-44123 Comment in transaction screen blocked by JIRA Workflow Step Property jira.permission.comment.denied
- Closed