I have 2 accounts in Jira, one is authenticated through AD and the other is in the internal directory. Both accounts are in the jira-administrators group which is in the admin role on all projects and that role has browse, create and link permissions in permission schemes. I have the same setup in Confluence using the confluence-administrators group. When I try to create a new Jira issue from a row in a Confluence table, I only see these 4 Jira 'target' projects listed.
Why can't I see all projects in the list with my AD authenticated account? The one in the Internal Directory gives me a list of all Jira projects as expected. I've spent plenty of time Googling this issue and folks generally say it's a permission issue. Quite frankly I'm tired of chasing this gremlin and need a straight answer!
Thanks in advance!
Don't hate me for saying this but it does sound like a permissions issue. That being said let's see if we can figure out why it's happening. You mentioned that you have an AD user and an internal directory users who are seeing different thing. Are all other AD users experiencing this as well (by that I men not seeing projects they should have access to see)? At the same time are other internal directory users able to see all projects they should?
You mentioned that the Admin Role is set on all of the permission schemes, am I correct in assuming that you are using multiple permissions schemes? and of the 4 projects that you can see does that set of 4 share the same permission scheme? And on that same note of the projects that you can't see do any of them share the same permission scheme as any of the projects that you can see.
Just a few ideas that might help start to unravel this mystery.
I hope that helps, and if not please feel free to reply back, we'll get this thing sorted out.
Hi @Jimmy_Seddon ,
I've looked at several other users' authenticated accounts using SU for Confluence and it appears they're able to see the correct list of Jira projects. To answer your questions, yes, I assign a unique permission scheme to each project with very few exceptions and no, the 4 projects I can see don't share a permission scheme.
It's very odd that my account in the Jira internal directory can see all projects in Confluence and that account is in the same groups that as my authenticated.
Open to your thoughts & ideas ...
I changed the permission scheme for project A, which I was able to see, to use the scheme for project B, which I'm not able to see. and it removed project A and added another project; not the one I was expecting.
Generally, when I create a project, I copy an existing permission scheme that already has most of the grants I need so I don't have to create it from scratch; then I rename it for the new project. I don't think this should be an issue, should it?
Puzzling to say the least!!
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events