My company just began using JIRA for bug tracking and so we're all pretty new to it. We make a software tool used by various customers to test and debug hardware under development. Because of the proprietary nature of details included in issues filed against our software by our customers I need a way to cleanly segregate each customers access to issues from one another while at the same time allowing our internal developers and testers full access to all issues. I'm thinking this is best handled by an issue level group permissions schema. I would also need a way to ensure that when a new issue is filed by any member of a particular customer group that issue is available by default to only other members of that customer group and our internal employees group.
It looks like issue level security might work for this, but I'd need to know my schema implementation is foolproof and that customers wouldn't even be able to see issue descriptions or names of other permissions groups while browsing.
Any advice would be appreciated.. thanks!
I think your approach is correct. But you would need to test it to make sure that your specific exact needs are met. My recommendation here would be to trial this in a test project. If you run into specific issues, then you can reach out to us for support.
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