nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Users unable to select epics from a certain project on issues in another project

Gabriela Cubeiro

We have a big picture tracking project where we have our epics, and link issues in our sprint in another project to these epics. My developers do not see the epics from our tracking project in the dropdown on the edit issue. It's becoming a serious bottle neck because only administrators can do this. I've reviewed permissions extensively, and don't know what I'm missing.

I would appreciate any insight!

Accepted answers

carolyn french

Hi Gabriela,

I'm trying to think through what permissions I would check in your situation.

Do your developers have Edit Issue permissions in the "tracking project"? In order to link issues, the user needs to have permissions to edit both issues.

Hope this helps!

Carolyn

All comments

carolyn french

Hi Gabriela,

I'm trying to think through what permissions I would check in your situation.

Do your developers have Edit Issue permissions in the "tracking project"? In order to link issues, the user needs to have permissions to edit both issues.

Hope this helps!

Carolyn

Gabriela Cubeiro

Hi Carolyn,

I reviewed both projects, and your answer helped me figure it out. Although I had granted the edit permission, I didn't realize the permission scheme I was using prevented the user for seeing the project. I'm still learning how all the different permission layers work.

Thank you for your help!

carolyn french

Awesome- glad to hear it!

Best of luck,
Carolyn

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

issue

jira

cloud

jira-cloud

permission

epic

link