What permission is required to see jiraProjectPage modules in the sidebar?

Jira Development Jira Cloud
,
1

I saw this question didn’t quite end successfully, and it’s the default behavior I would have expected. I’d have thought anyone with BROWSE_PROJECTS can see the sidebar item for a jiraProjectPage (unless the module limits it further with conditions). But that seems to not be the case. Even for logged in users, they can sometimes only see Issues (perhaps if they are not a user on a given Jira product type? But a user on other Jira products? But the project I’m seeing this on is also Limited access team-managed…)

Does anybody know which permission is the magic one? Or is there something else going on than permissions?

Cheers!
Adam

2

Hello @hitsthings,

I suspect that this is not a permissions issue.
Use the dev tools in your browser and confirm if you are getting any errors.

Browse Projects is all that is required. One needs to be authenticated as well.

3

It’s interesting. I think it’s related to the user not being allocated on the product. The user does have BROWSE_PROJECTS I think. If I run this from the Chrome console:

fetch("/rest/api/3/mypermissions?permissions=BROWSE_PROJECTS&projectId=10005", {
    method: 'GET',
    headers: { 'Accept': 'application/json', 'content-Type': 'application/json' }
})
.then(resp => resp.json())
.then(results => console.log(JSON.stringify(results, null, 2)))

I get

{
  "permissions": {
    "BROWSE_PROJECTS": {
      "id": "10",
      "key": "BROWSE_PROJECTS",
      "name": "Browse Projects",
      "type": "PROJECT",
      "description": "Ability to browse projects and the issues within them.",
      "havePermission": true
    }
  }
}

I assume that means the user has browse permissions agains the project? (Or am I holding it wrong?)

In the console there’s 403s for greenhopper endpoints.

4

You are correct,

I did confirm this with a test on one of my projects. "havePermission": true

Screenshot_20230903_113955
Screenshot_20230903_113955702×343 25.5 KB

On a side note, just remember that anything you run even in the console returns your permissions. You are logged in and the call is to “mypermissions”. It is not returning “the users” permissions

5

Of course:) In this case “the user” is a test account I created. So I’m logging in as that user.

So it sounds like BROWSE_PROJECTS plus having the User role against the project’s Jira product type are both needed. (Perhaps there’s more to it, but that’s the level of my mental model so far).

Thanks for walking through it with me!

1 Like