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; } } }

JIRA Agile Permissions

unknown

Permissions tied to project Administrator role

Why does JIRA Agile require the user to be an administrator on ALL the projects included in the boards filter in order to create sprints? Why is it not sufficient to simply manage these permissions using the configured boards administrators?

Assigning issues to a sprint on issue create

Why do some users get a sprint drop down on the create issue screen and not others? The differences are not related being project admins or boards admins.

Accepted answers

Nic Brough -Adaptavist-

1. Because sprints implicitly change admin settings on projects, so you need project admin rights (This is an issue that is entwined with "make admin rights more granular", and it's a bit of a hangover too - Agile is an add-on to Jira and re-uses it's permissions, in a less than ideal way. Atlassian have got a review of permissions for admins in progress at the moment)

2. Ah, you have to have the right to add issues into a sprint to get the dropdown. That means both "edit" rights, AND "schedule". It's usually the second that's missing...

All comments

Nic Brough -Adaptavist-

2. Ah, you have to have the right to add issues into a sprint to get the dropdown. That means both "edit" rights, AND "schedule". It's usually the second that's missing...

unknown

Hi Nic,

Thanks for the response, apologies in taking so long to reply.

Permissions tied to project Administrator role

How do sprints implicitly change admin settings on projects? If so what settings. Still not clear on this or the need.

Assigning issues to a sprint on issue create

Thanks.

Nic Brough -Adaptavist-

Sprints hook into the version functionality (although this should be completely detangled soon, if not done the last few releases of Agile). I think this is more a structural thing in Jira now - it simply doesn't have the granular permissions we'd like (yet) and it's a far more common practice to need to limit the owenership of a sprint to a scrum-master type role (who is far more likely to be well aligned with a project-owner type role than "any old developer"). It's improving,and I'm pretty sure it'll be broken up better soon. But for now "you have to be a project-owner type" is the right approach, given the current limits.

Not sure you have another question about putting issues into sprints here?

Welcome!

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

Quick Links

Find more posts tagged with

jira-software

permission