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

Creating one issue after another on workflow transition using JMWE

Sina Esfahani

Hi,

I have come up with TWO separate post functions to be executed when there is a transition from one status to another.

The problem is, when I transition, it only executes the first post function, and skips the other one. Both post functions have conditional statement, but I don't think that's causing the issue. Could there be another reason why it skips one?

Accepted answers

David Fischer

The only thing that can cause the second post function to be skipped is an error in the first, but then the entire Transition will be rolled back and an error will be displayed to the user.

Therefore, it is most likely the condition that returns false.

All comments

David Fischer

The only thing that can cause the second post function to be skipped is an error in the first, but then the entire Transition will be rolled back and an error will be displayed to the user.

Therefore, it is most likely the condition that returns false.

Sina Esfahani

Hi David, but each post function on their own execute and I see the results: the new ticket is created. I switched the order and the first one always executes and I see the result.

Also, are there error logs that I can check for JMWE?

David Fischer

The logs are written to the standard Jira log file (atlassian-jira.log)

You can also open a support request at https://innovalog.atlassian.net/servicedesk/customer/portal/8

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

transition

groovy

workflow

addon-com.innovalog.jmwe.jira-misc-workflow-extensions

jira-misc-workflow-extensions