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

Where do I debug the Jira Misc Workflow Extensions??!!

scott.fawcett

A while back we had 3 tickets that seemingly randomly changed status (from Released to In Progress). The Status was changed by the Jira Misc Workflow Extensions. Somehow, after hours of digging, I found why...and thought I had fixed it.

Now, months later, it happened again yesterday. For the life of me I can't find where the workflow is affected by this extension.

If you could point me in the right direction I'd really appreciate it. I've poked all around the workflow.

Accepted answers

All comments

John Funk

Hi Scott,

Did you look at the Post Functions on the Transitions in the workflow associated with the project where it happened? There is might be an auto-transition on another previous transition that is firing.

David Fischer

Hi Scott,

you should go to the JMWE Logs admin page and filter by the issue key that was transitioned. This will show you the post-functions that run on that issue. However, if the post-function that transitioned the issue is actually a Transition Linked Issues post-function or a Transition Parent Issue post-function run on another issue, then you won't find any logs because these post-functions don't log the _target_ issues they transition, only the issue on which the post-function runs (the issue being transitioned by the user).

If that's what's happening, you can filter the logs by post-function name instead - look for the Transition Linked Issues post-function and then the Transition Parent Issue post-function, if you see any execution then you'll need to check these post-functions.

scott.fawcett

I did...which adds a little to the confusion. In this specific case it's moving from Released to Needs Requirements.

For ALL (because All is configured as a transition input to Needs Requirement) there's nothing that references JMWE. And nothing looks abnormal.
For Update Resolution there's nothing that references JMWE.
For Released the first post function references JMWE. Here it is:

For each issue linked to the current issue through the relates to link type, the first applicable transition from this list will be triggered on that issue:

Released Awaiting Feedback of any workflow

Run as current user. A comment will be provided to the transition screen with the following text: Ticket has been released! Please confirm with your client it has met their need..

There are also 2 errors and 2 warnings. The errors are Post-function "Transition linked issues" errors. The errors are "Found no transition available for issue MSD-745"...which reference a Service Desk ticket. Maybe I need to look there (we create tickets in this project from Service Desk tickets). Although the error and warming timestamps don't coincide with the Status change. The errors occurred 3 weeks later (and I suspect it was when the parent ticket was changed back to Released and possibly attempted to trigger a change to the originating ticket in the MSD project).

There are 4 Relates To tickets linked.

One of them is at Needs Requirements and I don't see anything odd that would related to this.
Two of them were Released. Nothing odd.
For one of them, JWME set the Status FROM Needs Requirements TO Needs Requirements (odd) at the same timestamp the parent ticket was changed back to Needs Requirement. That must be a clue. But...same question. What changed this child ticket to Needs Requirement (when it was already at Needs Requirement)?

scott.fawcett

unfortunately the log doesn't go back far enough. I only have a couple days of logged info. The transition occurred 3 weeks ago, but was just noticed yesterday.

David Fischer

You apprently checked the post-functions on all transitions that can lead the parent issue back to "Needs Requirement", and the only one you found was on a transition from Released to Needs Requirements, and it triggers a "Released Awaiting Feedback" transition. What does that transition do? Also, it would have added a comment on the linked issues, and that doesn't seem to be the case.

Also, since the Status change made by JMWE is from "Needs Requirements" to "Needs Requirements", that means JMWE triggered a transition that _can_ start from "Needs Requirements" and that leads to "Needs Requirements". Do you have any like that?

Finally, when the parent ticket was changed back to Needs Requirement, can you check in the parent history who the user was who made the change (to the Status field)?

David Fischer

Oh, and also don't discount the possibility that the workflow was modfied since the problem happened 3 weeks ago...

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