We have conflicting requirements that:
The compromise that we found is that, when an issue is closed, its summary and description should be made public (after some manual check), but not comments and attachments.
Now, we need to implement this :-)
Comments can be worked out, since there is a visibility field on them, but the visibility of attachments is the same as the issue they're on. (There are several long-outstanding improvement requests related to this: JRA-6185, JRA-3893, ...)
Here are a few workarounds we could think of:
All of this seems rather clumsy... Would you have a better solution? Or what would you consider the less ugly one?
Samuel, you could try our add-on - Smart Attachments (https://marketplace.atlassian.com/plugins/com.stiltsoft.jira.smart-attachments). It allows you to delegate access to particular attachment categories for the appropriate user groups. So you can easily restrict access to attachment categories that will be hidden. You can find details at https://docs.stiltsoft.com/display/CATAT/Managing+Categories. Thanks.
We once did a Confluence macro (as an opensocial gadget) for a client to do something similar. It was basically the JIRA Issues macro with no hyperlinks and you could expand each issue to view certain fields. The JIRA XML view as all of the details about the ticket so an opensocial gadget allows you to easily decide which elements to display and which to hide. This allows you to publically show whatever details you want and still have the full ticket available internally.
I don't love this idea but you should be able to use a field configuration scheme to hide the attachments field. What I don't love is that they are based on issue type and not status/resolution so you'd still have to change the issue type or project that your closed tickets are in so that your 'hidden attachment' scheme would be used and your internal devs wouldn't have access to the attachments either.
Hi, not sure if this will be appropriate for you but I have a plugin called Attachment Permissions (https://marketplace.atlassian.com/1212271) that allows you to restrict visibility of attachments to a user group and/or reporter, assignee and creator. This isn't just for open and closed JIRAs but if access is restricted to creator, assignee and reporter than only these users would have access when the JIRA is closed.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG