I’m working with JIRA and need to configure one specific project so that anyone can view its issues without needing to authenticate or create an account. The goal is to allow external users and stakeholders to browse through tickets and their details without going through a login process. However, I want to make sure that all my other projects remain secure and accessible only to authorized team members. Is this kind of mixed visibility setup possible in JIRA? What configuration steps would I need to follow to achieve this? I’m looking for a way to balance transparency for one project while maintaining privacy for the rest of my workspace.
yeah, totally doable. just check your global settings first - anonymous users need basic access enabled before project permissions kick in. fair warning though: once you flip this on, search engines might start crawling your public issues.
Enabling anonymous access in JIRA is achievable through tailored permission schemes. You can create a new scheme specifically for the project in question, granting ‘Browse Projects’ and ‘View Issues’ permissions to ‘Anonymous Users.’ Ensure that the other projects maintain their original settings for security. To do this, navigate to Administration > Issues > Permission Schemes, establish the new scheme, and apply it to the desired project. Furthermore, be cautious about what fields and comments are visible to anonymous users, as sensitive information could be inadvertently shared. Note that these users won’t have permissions to create issues or leave comments, so adjusting your workflow may be necessary. This approach significantly increased our project visibility while keeping everything else private.
To enable anonymous access for a JIRA project, start by navigating to Administration > System > Global Permissions and grant ‘Anonymous Users’ the ‘JIRA Users’ permission. Next, create a new permission scheme dedicated to your project, ensuring to include ‘Browse Projects’ and ‘View Issues’ for anonymous users. It’s crucial to verify that your other projects maintain their existing permissions to avoid unintended exposure. I’ve implemented this approach, and it effectively balances visibility with the security of other projects. However, be aware that high traffic from anonymous users could impact performance.