Setting Up Scrum with Specific Access Permissions

[Viann Tang]

I am reaching out to inquire about the feasibility of setting up a Scrum project in Jira with specific access permissions.

Our goal is to allow everyone within our organization to have access to view the contents of specific issues received via email or external links. However, we would like to restrict their access to only those particular issues and prevent them from viewing other issues within the project.

We have explored the project permissions and issue permissions settings in Jira. However, we couldn't find a direct way to achieve this specific setup.

Could you please provide guidance on how we can configure Jira to meet these access requirements? Is it possible to implement such a setup using Scrum methodology in Jira? If so, what steps or configurations would be involved?

Any insights, recommendations, or best practices you can share would be greatly appreciated. We value your expertise and look forward to your guidance in this matter.

Thank you very much for your attention to this inquiry. We eagerly await your response.

[Ollie Guan]

Hi @Viann Tang ,

You need to pre-set these restrictions, not to control by mail sending scope.

Issue-level security is probably the easiest way.

https://confluence.atlassian.com/adminjiraserver/configuring-issue-level-security-938847117.html

[Viann Tang]

Hi Ollie,

Thanks for your kindly replay!! Let me try it first.

[Viann Tang]

HI @Ollie Guan ,

Issue-level security is probably the easiest way. However, if we only want to share specific stories with certain individuals and prevent them from accessing other stories in the project without a direct link, we need to assess if it is feasible.