Linking to Jira Software Permissions
Asked by Jared:

We have a small team of developers working on Kanbans in Jira Software. And therefore have premium for a team of 10. We were hoping we could get our 10 stakeholders access to just the general information (Ticket name, updated, last comment)   

I created a confluence page and have inserted the Software Macro. The table is configured and working when I view it.   

When an end user goes to the link, they get the error "JIRA Project doesn't exist or you don't have the permission to view it."  

I have added the jira group to the filter permissions  
I have added the jira group to the "Browse Projects" Permission in the board settings  

Once I added the user to the Jira Software product, the table appeared.   

Is it a true statement to say that in order to view the issue status on a kanban on a confluence page, the user has to be a licensed Jira Software user?   

If false, then what am I missing?  
If true, is there another way to make this work?   
(I hear I should be able to set permissions to public but 1. I would rather not and 2. I do not see that as an option.   
![Snag_1ce5b2ab.png](https://community.atlassian.com/t5/image/serverpage/image-id/193558iD0529F26D0E7A184/image-size/large?v=v2&px=999 "Snag_1ce5b2ab.png")![Snag_1ce5bba4.png](https://community.atlassian.com/t5/image/serverpage/image-id/193559iF58CC505115B6081/image-size/large?v=v2&px=999 "Snag_1ce5bba4.png")


Answers:
author: Mikael Sandberg
body: What you see is expected. The user has to be able to browse the project in order to be able to see the issues in Jira. If you have stakeholders that do not have/need access to Jira, one option would be to change the permission scheme for the project and add Public to the browse project. But then you are opening up the project for anyone on the internet.

comments: author: Jared
body: Thanks Mikael,

I have a follow up question to your answer.  

We are using Atlassian Access for single sign-on.   
I know our service desk we only have 9 agents (Licensed users)  
Anyone within our domain can authenticate with SSO and fill out a ticket, and also review the suggested "How-To's" that get suggested.   

How is that working? Is our knowledge base open to the public? But then some other global rule is locking it down to our domain via SSO?  

Is there a way to apply this kind of permission to other projects like Jira Software?  
So that I could make the project open to the public, but then restrict it to only people authenticating with Atlassian Access?  

Thanks!


author: Mikael Sandberg
body: So it depends on how you have configured your customer permissions in JSM. Any user that is defined as a customer have free access to the KB and can submit requests via the portal without having a license. By default your global permissions are set to only allow users that have access to your instance to be customers, so that would mean all users that are synced via Atlassian Access.

JSW does not have this feature, in JSW you have to have a JSW license assigned to your account in order have access to those projects.


author: Curt Holley
body: It is true:

*Is it a true statement to say that in order to view the issue status on a kanban on a confluence page, the user has to be a licensed Jira Software user?*

To be more precise, they need permissions to view the issues that form the content of the Jira macro, to be able to see that content on a confluence page.


Tags: cloud

confluence-cloud

macro

report