I’m having trouble setting up my JIRA project so that anyone on the internet can view issues without logging in. I want it to work like GitLab, BitBucket, or GitHub where:
- Any internet user can see issues without an account
- Logged-in users can create and comment on issues
I’ve got a cloud JIRA Core + Software license for an open source project. Right now, if someone tries to view an issue, they just get a login prompt.
I’ve already tried:
- Changing permissions to ‘anyone’ in the Default permission scheme
- Checking ‘Anyone can join’ in Site access settings
- Adjusting Issue security settings
But nothing seems to work. The permissions options I see in other guides don’t match what I have available.
Has anyone gotten this working? What am I missing? I really want to make my project’s issues publicly visible.
yo, i feel ur pain. jira cloud’s a real pain for public stuff. have u tried using the jira REST API? u could build a simple webpage that pulls issue data and shows it publicly. bit of a hassle, but it works. or maybe look into those issue-mirroring tools that sync jira with public boards. good luck!
I’ve faced a similar challenge with JIRA Cloud, and unfortunately, it’s not straightforward to achieve what you’re looking for. Unlike self-hosted JIRA, Cloud doesn’t offer a built-in way to make issues publicly visible without authentication.
One workaround I’ve used is integrating JIRA with a third-party tool like JiraPS. It allows you to create a public-facing portal that syncs with your JIRA issues. This way, you can control what’s visible publicly while maintaining JIRA’s security.
Another option is to use JIRA’s REST API to create a custom frontend. This requires more development work but gives you full control over the public interface.
Ultimately, if public visibility is crucial, you might want to consider alternatives like GitHub Issues or GitLab, which are designed for open-source projects and offer better public access out of the box.
As someone who’s worked with JIRA Cloud extensively, I can tell you it’s not designed for public access out of the box. It’s frustrating, I know. One solution that worked for me was using a JIRA add-on called ‘Issue Collector’. It lets you embed a form on a public webpage where users can submit issues without logging in. These submissions then appear in your JIRA project.
Another approach is setting up a separate public-facing system like Trello or a simple WordPress site, then using Zapier or a similar automation tool to sync it with JIRA. This way, you maintain JIRA’s robust features internally while providing a public interface.
Remember, though, these are workarounds. If public visibility is a must-have, you might want to reconsider your tool choice. JIRA’s strength is in internal team collaboration, not public issue tracking.