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

Is it possible to prevent users from verifying an issue, if they resolved it?

Guido Wilken

As we are a small group of developers we do not have a dedicated QA team which could be reflected as a group or permission in Jira.

We still want to introduce a "four eyes rule". If someone resolved an issue he should not be able to verify it by himself. Is there a way to reflect this in the issue workflow? I didn't see anything like it....

Thanks!

Guido

Accepted answers

All comments

Guido Wilken

Thanks guys!

What I actually want to achieve is, that I don't need specific roles or permissions for people who are able to review bugs. That's what I currently have...

We have a team of 5 people working on a project and everybody should be able resolve AND verify. The only thing I want to prevent, is that the same person who resolved an issue is able to verify it.

Thus having at least 2 persons taking a look at each issue without specifying a specific QA role...

Jobin Kuruvilla [Adaptavist]

You can add ny step in the workflow you want. But the default workflow itself covers this is a small way. There are 2 steps, 'Resolve Issue' and 'Close Issue'. The person who actually fixes the issue 'Resolves' it where as another one, normally the one who reported it or a tester, verifies the issue and 'Closes' it.

To add a 'Verify' workflow action is pretty common too!

Ramiro P

Ouch! I forgot about the 'Close' and 'Resolve'. It is much easier that way! Good one!

Ramiro P

Yes there is. You can configure it in the workflow in many ways. For example:

-You can have someone in a QA rol inside the project who is the only that can approve the issue.

-You can set up a condition that only the project leader can approve the issue.

Here is a doc where you can find out how to configure the workflows, but I think Atlassian is having trouble in the confluence pages.

Jobin Kuruvilla [Adaptavist]

@guido might also want to add some conditions etc which prevents the person who resolved it to close it as well. Maybe add a post function in the 'Resolve' action to assign it to someone else and then allow only the assignee to 'Close' the issue.

Ramiro P

Yes, that could be a solution. If you assign to other person and the issue can be resolved only by the assigned user... Yes, that will do the thing.

Or maybe you can set a condition that indicates you need at least a vote for the issue to be closed, so other user or maybe two need to vote the issue before it can be closed.

Ramiro P

There is an option to add a condition called 'Value Field'. There you can choose the field 'Votes' and indicate that should be grater than 1

Guido Wilken

Mmh, I don't see any condition to check for votes.

And as well, the voting is usually done before resolving the issue, right?

Ramiro P

And the voting can be done since the issue is created. I'm using in a issue type called 'Documentation' where the issue needs to have 2 votes to be accepted.

Jobin Kuruvilla [Adaptavist]

Good poiint above the 'Value Field' check!

JamieA

If you don't want to dick about with custom fields, you could use the scripted condition from the script runner plugin. The actual condition is below.

import com.atlassian.jira.ComponentManager

def componentManager = ComponentManager.getInstance()

def resolutionRecords = componentManager.getChangeHistoryManager().getAllChangeItems(issue).findAll {
    it.field == "resolution" &amp;&amp; it.fromValue == null &amp;&amp; it.toValue != null
}
return !resolutionRecords || resolutionRecords.last().user != componentManager.jiraAuthenticationContext.user?.name

Guido Wilken

unfortunately it's not working yet.

I won't be able to continue testing until Monday...

I'll keep you posted!

Ramiro P

Let know if you found the solution to this issue.

Ramiro P

Hi Guido,

I found a condition that could be very useful. It's called 'Separation of Duties Condition'

And this is the description: Condition to prevent a user to perform a transition when he has already performed another.

Take a look when you can. I think this is what you are looking for

Welcome!

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

Quick Links

Find more posts tagged with

jira

permission