How can I automatically enforce a default comment visibility restriction?

[Jyoti Kumari]

Hello Everyone,

How can I automatically enforce a default comment visibility restriction (e.g., to a specific Project Role or Group) for new comments in a designated Jira Cloud project, specifically using a Forge application or a native REST API call?Kindly suggest.

Thanks and Regards,

Jyoti

[Sunny Ape]

Hello @Jyoti Kumari 

In addition to what @Nikola Perisic has said, the Update Comment endpoint does allow you to set a comment's visibility to a particular group or role, but it requires that the comment already exists, because the endpoint needs to know the ID of that comment

You'd need a convoluted workflow that, when a new comment was added to the Work Item, it used the Get Comments endpoint to get a list of all the IDs of all the comments, somehow compare that list of IDs to a prior list of existing comment IDs to find which one was the new one, then used the ID of that new comment to set its visibility, then added that new comment's ID to the existing IDs list. This is a seriously non-trivial task for a native Jira workflow

However, if you are a moderately proficient Forge developer, you should not have any problems converting the logic of what I just described into an app for your Jira Cloud instance.

[Nikola Perisic]

Hello @Jyoti Kumari 

Automatically no, but manually you can do this when the comment is being made there is a lock icon near the comment where you can limit on which roles will be seeing the comment.