Execute transition / Change status complex issue

Issue #349 resolved
Andrey Kiyanovsky created an issue

Hi Fidel,

I again have an issue with complex transitions.

Steps to reproduce.

1) "Migration" task upon transition to "Production" status executes "Release" transition on linked issues and write a comment with the list of issues.



2) "Release" transitions write the field "Deployed" and change status to the desired on the same issue.


3) I see that "Release" transition is called on all linked issues, because "Deployed" field always changes its value.

4) But when we have more than one linked issue, the first issue never been transitioned to the new status.

This issue is never transitioned

Right transition activity TD-785

Bad transition activity TD-786

As you can see, in TD-786 issue change status to "Ready for QA" doesn't work.

No matter how many issues I have in the list, the first issue is never transitioned to the "Ready for QA" status.

5) There is an error message in the JIRA log, attached.

I've tried to change execute/delayed execute and change status/delayed change status, but it doesn't help.

I've written all the required fields to ephemeral strings before changing status to "Ready for QA", it doesn't help.

I've tested with completely different issue lists - nothing changes.

I've updated JWT from beta 7 to 2.2.12, doesn't help.

I have no more ideas... Please help.

Thank you in advance, AK.

Comments (10)

  1. Fidel Castro Armario repo owner

    Hi Andrey,

    Please, try replacing Release as source value in transition to "Production" status in "Migration" task's workflow with the following text:

    Release : {delay=1000}

    if it doesn't work, please, try this:

    Release : {delay=2000}

    this we we are forcing a delay of 1 s or 2 s before trying to execute "Release" transition, instead of the default delay of 0.5 s.

  2. Andrey Kiyanovsky reporter

    Thank you for the prompt reply, bit it did not help (

    Forgot to say, that if I have only one linked issue, it is transitioned as expected.

  3. Andrey Kiyanovsky reporter

    Maybe I should insert the delay inside "Release" post-function, when issue changes status to the "Ready for QA"? Because "Release" transition always works.

  4. Fidel Castro Armario repo owner

    Yes, Andrey, good suggestion. Please, try adding the following term to 4th post-function in "Release" transitions:

    + " : {delay=1000}"

    if it doesn't work try this:

    + " : {delay=2000}"

    if none of this work, please, set logging level for package com.fca.jira.plugins.workflowToolbox to DEBUG. Then reproduce the problem, and share with me the part of your server's log file implied in the problem. You can send it to support@workflowarts.com.

  5. Andrey Kiyanovsky reporter

    Fidel, it works both with 1000 and 2000 delays! Thank you very much!

    Could you please tell me what is the default logging level should be set for the workflowToolbox package?

  6. Fidel Castro Armario repo owner

    Great!. I recommend you to use 1000 as delay, and ERROR as default logging level.

  7. Log in to comment