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 can add issue to "Sprint" field of different project

Arjon Buikstra

We just solved an issue where a user had added a demo issue within a sandbox environment to a live sprint that was just about to start. Upon attempting to start the sprint, the Project Manager of the live project received an error stating he needed Administrative priveleges over the Sandbox project.

My question is: how do I prevent people that administer project A that do not have any priveleges for Project B in adding issues to sprints belonging to Project B? I do not want to remove the 'Sprint' field from the screen, as it's also visual feedback for the actual users of this functionality.

Accepted answers

Julian_j3j898

Hello Arjon,

It appears that it is not possible for now, where it should be. This could led to a confusion as the sprint field will still populating any Sprint regardless of the project or permission. It appears that this have raised as a story in our issue tracker system:

https://jira.atlassian.com/browse/GHS-10805

I would like to suggest you to watch, vote and add a comment on the ticket, so the developer could review it.

Hope this information could be useful.

Regards, Julian.

All comments

Arjon Buikstra

Incidentally, the sprint was started after removing the 'Sprint' entry from the Sandbox project's issue.

Julian_j3j898

Hello Arjon,

https://jira.atlassian.com/browse/GHS-10805

I would like to suggest you to watch, vote and add a comment on the ticket, so the developer could review it.

Hope this information could be useful.

Regards, Julian.

JamieA

This ticket should also mention Arkon's point about a potential DoS-like circumstance, where a user can easily prevent people from starting sprints.

Arjon Buikstra

Thanks for pointing out the ticket Julian. I wish I could upvote it once for every user affected by it, as although not all visitors to this forum have an enterprise setup for JIRA with many projects in one instance, it does affect many more users with only me reporting it.

I'll keep an eye on the progress.

Arjon Buikstra

And it seems this ticket was closed off as unnecessary... big shame. Would've been a useful addition for multi-project environments.

Welcome!

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

Quick Links

Find more posts tagged with

jira-software

jira-administration