We are working with a client who would like visibility into the changes we put in our system for their requirements. As we do not want them to have full visbility to issues which do not concern them we can simply not give them browse access to the projects in question, however reporter access seems appropriate.
However, there are issues which are created by us, and not the client, which we would also like to make available to the user. Is it possible to grant access to these issues based on the label applied, or the component indicated, or does this need to be done issue by issue (i.e. granular access)?
So those other issues which was created by you, are not actually all the issues which are available in that project. Am I correct?
In the case if you want to grant them to acess all the issues in the project whether he is the reporter or not, you can define Issue-Level security scheme, and define it to be for that user and your company. This will make them able to see the issues in that project. For more information, please refer to the link:
However, if it's not the case, please let me know. :)
I'd also go for issue security levels. You can bulk restrict all issues and change the level for those issues you want your customer to be able to view. Maybe you could even think about a listener that automatically changes the level based on a custom field (I'm not sure if I'd go for labels)
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs