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!
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.
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.
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?
Which version of JMWE and JIRA are you using?
There might be a case issue since JIRA 6 (https://developer.atlassian.com/display/JIRADEV/Renamable+Users+in+JIRA+6.0)
I will create a snapshot build with a potential fix and more logs.
Could you raise an issue on https://innovalog.atlassian.net, so that we can better track this?
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hi, everyone! Molly here from the Jira Service Desk Product Marketing Team :). In the spirit of this month's august-challenge, we're sourcing stories of Jira Service Desk activation fro...
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!
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