Four years later… is there any chance that this could happen before the end of this year? Particularly with auditing and ISO change control requirements, we really don't want all of our developers and QA to need admin rights to the build plans.

Also the ability to link a Jira issue should be tied to the same permission used to quarantine an issue.

i partially agree with msilhavy, I think the quarantine permission should be place next to build (see image below), this way the permission management would be a little bit more fine grained.

I agree that a quick and simple fix is to add quarantine ability to the BUILD permission - adding it to any other category does not make sense to me. Also, plan admins should retain the ability to quarantine, so I disagree with the current summary of this issue.

I totally agree that the Build permission (or even Edit) is enough.

This would be extremely helpful to us as well. We have a small group of people who administer bamboo and our plan configurations. Developers and QA need to be able to quarantine a test without having to ask someone else to do it for them.

Thanks for your feedback.

@James i think Build permission would suffice or in a new Permission level called Test which include other things later.

In an ideal world, where permissions move into a more JIRA-like model of Permission Schemes, Quarantine would be its own level; that said, if you simply allowed users with "build" permissions to quarantine, that would cover 90+% of our situation.

If we were to change this, what would be the appropriate permission level here?