JMWE - Separation of duties challenge

Hi all,

currently I am having a challenge with the JMWE-plugin, namely with the "separation of duties"-condition.

We've got the classic case: While one colleague shall be able to "resolve" an issue, he must not be able to "close" the same issue (and vice versa).

What I did: In the "close issue"-transition I've added a JMWE-condition (only that condition!):

"Only a user who has never transitioned the issue from In Progress to Resolved can execute this transition."


1.) If I resolve an issue, I cannot close the issue (right!), anybody else can close it (right!)

2.) If anybody else resolves an issue, I can close it (right!), but the "resolver" himself can close it as well (wrong!)

This is quite strange and difficult to debug, as it seems to work only partially as required and expected. As mentioned no other conditions apply to the "close issue" transition.

I am project lead (we even temporarily changed that) and in the same roles as the other testing colleagues.

Anyone any idea? Hints are highly appreciated!


4 answers

1 accepted

1 vote
Accepted answer

The problem will be fixed in the upcoming 3.2.0 release, which should be available this week.

Have you looked at the JIRA logs? Search for "com.innovalog".

Also, have you verified that the transition from In Progress to Resolved appears in the issue history with the right user?

Hi David,

thanks for your lightspeed-answer!

Add 1: at which point you expect a message from "com.innovalog" in the logfiles? When the issue is transitioned from "in progress" to status "resolved", preventing the transition-button "close issue" to show up?

Add 2: The transition in the history is done with the correct user in all cases. Thanks for pointing to that, but here seems to be no error.



The log would show up when you try to trigger the Close transition (actually whenever you display the issue since that is when the Condition is evaluated, to build the list of available workflow actions).

So, I'll have a look in the logs and will come back with the result asap. Thanks!

To be more precise: the Condition scans the "issue history" for the issue, looking for an entry associated with the current user that shows a change for the "Status" field with an "Original value"=<from status> and a "New value"=<to status>

So you should verify the "History" tab for the issue that shows the inappropriate behavior.

Hi David,

thanks for your precise description regarding the "issue history". As our current log level does not show any "com.innovalog" entries, we will increase logging as soon as we can schedule a maintenance downtime.

Meanwhile I can post two screenshots. One showing the history tab, where user "J" is able to close the issue, although the workflow JMWE-condition does implicate he should not (second screenshot).

Most likely you agree that this is kind of a not expected behavior, right?


Second screenshot:

Which version of JMWE and JIRA are you using?

There might be a case issue since JIRA 6 (

I will create a snapshot build with a potential fix and more logs.

Could you raise an issue on, so that we can better track this?

Which version of JMWE and JIRA are you using?

We're using JIRA 6.0.5 and JMWE 3.1.1

Could you raise an issue on,

and I created JMWE-206 :)

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,104 views 4 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you