We allow people outside of R&D to have access to JIRA so they can submit requirements and track bugs, but we'd like to be able to limit the types of issues they can look at. For instance, if an SE happens to know a user story issue ID, we'd like to be able to keep them from looking at those issues.
Is something like this possible?
Not natively. The best you can do is use security levels to hide issues, possibly setting the security level with a post-function (as you can have different workflows by issue type, you can set the level on an issue-type basis)
You'll also probably want to think about how you stop people creating issues that they then won't be able to see. It's not possible to stop people creating your "restricted" issue types without code.
In short, it may be a LOT easier to simply split the data into two projects, one for R&D and one for the rest of your users, then use boards to view stuff across two projects
We have a project for requirements and another one for HF requests that help prevent people outside of R&D from creating work items they can't edit. Still, we'd like for them to be able to view any bugs, even if they were generated internally. I'll try out the security levels approach soon and report back.
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