Can we support Collaborator-JIRA Integration without creating an additional JIRA user?

Question

Why does admin get Browse Project Permission error when admin has this permission? We are using JIRA 7.7.

Our user 'admin' is a member of Jira-system-administrators.

Project permission schemes for all projects granted Browse Projects to group Jira-system-administrators. All Projects are Software projects.

Yet when user admin selects "Projects", on main page and chooses "Software", admin gets a Browse Project Permission Error, "You don't have the 'Browse Projects' permission..."

For us 'admin' can view anything, and should be able to create issues too, but cannot. What are we doing wrong?

Lots of failures when choosing issues assigned to me when logged in as admin, and cannot view or create any issues either.

The real goal here was to allow Collaborator to create/view issues without having to create a generic JIRA user.  I was hoping to enable JIRA users to create Collaborator reviews and Collaborator reviewers to create JIRA issues, and/or transition JIRA issues as per their workflow. We have a limited number of licenses, and I hate using a license to create an integration user in JIRA, but presently I see no other viable alternative.

Any help would be greatly appreciated. Thank you.

Andy Heinzer · Answer

Just because this user has create and delete issue permissions, does not grant them access to be able to actually see the issues in the project.

Did you test the user for the "Browse Project" permission?

If the user has the browse project permission for this project, but still cannot see the issue in that project (when trying to browse to it directly), then I think it's safe to say that permissions are not actually the problem here.

Instead your Jira instance could have been configured to use Issue level security.  If this is the case, then you need to look more closely at the security levels that are in use for that project.   It is possible that the permission scheme is setup to grant the user access to browse the project, but that all the issues in the project might be set to a security level that this specific user does not have.

Elicia Syson · Answer

I just tried the +/secure/admin/PermissionHelperAdmin.jspa and got to the Permission helper, but there is 'No Matches' for User admin when I am logged in as admin. So I tried logging in as myself, and as myself, using the same approach, and I could see User Admin, and the admin's permissions for a known issue, showed: Status:admin has all the Project Permissions, except View Development Tools, and for the Issue Permissions, only has permission to Create Issues and Delete Issues.

So I tried browsing as admin directly to a known issue, +/browse/<known-issue>, but admin cannot, Error: The issue you're trying to view can't be displayed. It may have been deleted or you don't have permission to view it right now. The issue is there, I can view it. So must be some permission issue still. Wonder which one. I suppose I could give admin permission to do everything, but I think our admin really should not have all those permissions. I was hoping for minimal duties for admin.

Also, thank you for taking the time to help.

Andy Heinzer · Answer

Without being able to view any issues, I cannot use the Jira Admin Helper.

Actually, that is not true if you are a Jira admin.   As a Jira admin you can still use this utility in the system administration menu.   Go to the Gear Icon -> System.  On the left sidebar menu there is a link to Permission helper.  The URL will be your Jira site + /secure/admin/PermissionHelperAdmin.jspa

On this page you can select the user, and issue, and a permission to check.  I suggest picking any issue in the project you want to browse.

Please try this.