Access to view tickets internal user copied in on within a Private project

Question

Hi.

I'm hoping someone can help with this.  I've recently created a new team managed project within my company for our Finance team to help them work more effectively/efficiently and give them transparency on types of issues being received.

The problem I'm experiencing is that because this is for our Finance team, they will be dealing with highly sensitive information therefore the project has to be set up as "Private", meaning only people who have specifically been given internal access (only Finance Team Members) can access this project.

This is causing major issues when either an internal or external customer emails in a request to the Finance team and copies in (or sends direct and copy finance team in) an internal user who does not have access to the project as they do not receive any notifications advising of the issue being raised and cannot access that particular issue.  Finance team are also unaware that the reporter has copied in an internal person who may be required to work within the issue.

Does anyone know of any way I can get around this problem so we can enable view/add internal comment to any issue that an internal user has been copied in on, but does not allow them access to any other issue within the project?

Thanks in advance!

Ste Wright · Answer

Hi @Kathryn Gerrell

Yes, you'd need to use Company-managed for this one.

The suggestion for allowing Issue Security Schemes in Team-managed is here, if you'd like to vote for it: https://jira.atlassian.com/browse/JSDCLOUD-8749

Ste

Kathryn Gerrell · Answer

Hi Ste,

Apologies for delay, I've been on annual leave.

Thank you for the steps you provided, I got as far as number 9 and I'm stuck!  Would you know if this can only be done in a Company managed project?  The project that requires this is Team managed and it just does not have a menu option of "Issue Security" within the project settings.

I'm a Jira Site Admin and I've even asked a Jira Org & Site Admin colleague and they also do not have this option in the relevant project settings menu.

Thanks

Ste Wright · Answer

Hi @Kathryn Gerrell

This is how I'd do it with an Issue Security Scheme (with instructions on how to create one):

* Go to Settings > Issues
* Select Issue Security Scheme from the left-hand menu
* Using the "Add issue security scheme" button, create a new scheme
* Next, press the hyperlink "Security Levels" on the right-hand side, in line with your newly created scheme
* Add a security level - eg. Default Level
* Next, press the "Add" hyperlink the Actions column, in line with your newly created level
* Add "Reporter" to the level, along with access for the Finance team (eg. Group, Project Role, etc)
* Finally, press the hyperlink "Default" in the Actions column, to ensure this scheme is set for every created issue
* Assign the scheme to your Project

You could add additional security levels if needed - eg. a level just for Finance which hides the issue even from the creator.

Now - you can't add Request Participants to an Issue Security Scheme (there's a suggestion for it though, see JSDCLOUD-3948) - but I would...

* Use Automation to copy the users into a separate field
* Use that field in the Issue Security Scheme instead

Ste