You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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!
It might be useful to use 2 Projects for this - for example...
^ You could then do the following...
An alternative - or these could be used in JSM also - is to use an Issue Security Scheme
You could limit the visibility of each issue to the Finance team, the creator/reporter, and request participants. That way Finance could see all tickets, but the creator only sees the one they created.
Thanks for your comments.
I did try and look into whether I was able to restrict the view so that the Reporter was only able to see issues they had created and the same for Request Participants i.e. they can see the issue too, but I can't see how I can do this?
I'm looking in Issue Security Scheme, but I'm really struggling to understand exactly what would need updating for me to set this up.
Are you able to advise at all?
Thanks in advance
This is how I'd do it with an Issue Security Scheme (with instructions on how to create one):
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...
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.