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

Segregation of Duties

elliott.day

Hi,

Is anyone aware of a method to prevent the creator (reporter) of an issue from moving the issue from the first status of a workflow?

Basically i'm looking for an anti 'only reporter' condition.

I cant use the segregation of duties condition since technically with the workflow going from create > first status, it hasn't been transitioned by a user.

I also cant seemingly use any groupings of users as the only approvers since there could be crossover with issue creators and approvers.

Thanks.

Accepted answers

Trudy P Claspill

Hello @elliott.day

Welcome to the community.

Are you working with a Classic project or a Next Gen project? It sounds like you might be using a Next Gen project.

All comments

Trudy P Claspill

Hello @elliott.day

Welcome to the community.

Are you working with a Classic project or a Next Gen project? It sounds like you might be using a Next Gen project.

elliott.day

Hi Trudy,

I'm just using a classic project.

Trudy P Claspill

Are you trying to prevent the reporter from selecting him/herself as the Approver of the issue, and thereby prevent them from transitioning the issue to an Approved status?

If so, it seems that is not possible with the OTB product. See https://jira.atlassian.com/browse/JSDCLOUD-6249

You would need an add-on to add the appropriate condition to the workflow transition to block the Reporter's access to the transition. This could be done with Adaptavist Scriptrunner, for example. See this post from 2018.

https://community.atlassian.com/t5/Jira-questions/Negative-condition-in-transition-change/qaq-p/230313

elliott.day

I've got a pre-determined group of approvers, however individuals within this group are also able to create the issues.

So rather than selecting themselves as approver they may already be within the list of approvers from that status. I'm just looking to segregate so that someone couldn't create and approve their own issue, even if they are fine to approve other individuals issues that hit the same status. Hope that makes sense.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud