Giving readonly access to Jira lists in Confluence pages for users not logged in to Confluence?

[Louise Kelstrup]

We have a confluence site which is used both internally in the organisation and with nearest collaborators for documentation, knowledge sharing etc.

Some of the pages are made public for everybody (including users not logged in) on the internet to see.

Many external users access our site to see our public pages. We don't know who they are. This is public information for everybody to see, if they want to. Like a Homepage.

We have recently started to move some of our Confluence content to Jira, because we need more workflow associated with the content. We have added Jira lists to Confluence pages and it works great. Confluence contains the same information as before.
When you are logged in, that is.
Now we have a problem.

Because some of the moved content is relevant for the general public. Only in readonly and only the information from Jira that we share in the Confluence page - the external people do not need to go to Jira and see any details and they never need to modify.

How do we setup the configuration to avoid removing information from the general public?

[Rina Nir · Accepted solution]

Hi @Louise Kelstrup 

As @Kathy Hart  mentioned, this will require anonymous access to Jira.

You could solve this using an App: checkout the App Jira Snapshots for Confluence  . The views of Jira data created by this App work differently then the native Jira lists in terms of permissions:
1. Anyone with view access to the Confluence page can see the Jira data that is put on this page
2. Only people with EDIT permissions on the Confluence page can refresh the data (by taking a new Snapshots)
3. The access to Jira relies on a configuration setting on the instance level- so relies on permissions of a selected user (not related to the Confluence user that is viewing the page)

(Disclosure: I am the CEO of RadBee, the makers of this App)

Hope this helps,
Rina

[Louise Kelstrup]

Thanks I'll look into this.

[Kathy Hart · Accepted solution]

I do not believe you can set them up where they are visible in Confluence, but not allow the public to also see the tickets in Jira. However, if you set your permissions correctly, viewing is all they would be able to do.

• These suggestions will work only if you are using a Cloud instance. It will be different for Data Center or Enterprise.
• First you must have a Site Admin allow public sharing of dashboards and filters in Jira:
  • Choose Settings(Cog wheel in upper right).
  • Choose System
  • Edit Settings
  • Turn Allow users to share dashboards and filters with the public to On
• To make the project and filter viewable by the public, you will need to update the Permission Scheme for the project and filter to include the Public group
• Add the Public Group to Browse Project only. This will allow them to see the tickets, but not interact with them.
• Next, make a Saved Jira Filter to populate the Jira Macro in Confluence.  The Filter Permissions will have to be set to allow the Public group to view the filter.
• Use the filter to populate your Jira Macro in Confluence.

The public will still be able to click on the ticket and be taken to Jira to view it, but they will be unable to interact with the ticket once there.

[Louise Kelstrup]

Thank you very much.

We are discussing in our org if this solution is the way to go.