Problem with JWT - Updating Label, Using Validator, and Automatic Transition

[MAG-II]

Hi Fidel -

I am having another problem with my workflow post functions/validators. What I currently have going on is Issue #1 and Issue #2. When an Issue #1 reaches a certain point in it's workflow it cannot advance to the next step due to a Validator that requires the label to read "Approved Prime Security"

I have a post function configured on Issue #2 workflow (same project) in that when it reaches a certain point it updates the linked Issue's label (Issue #1) to "Approved Prime Security." What also happens in that Post Function is that Issue #1 advances a step in its workflow. When I advance Issue #2 to the Post Function action I get an error message.

This action does work when I take the Label "Approved Prime Security" Validator away from Issue #1. Do you have any idea what I error I've made with the Label Validator and/or the update Label Post Function?

Much thanks in advance.

[MAG-II]

Issue #2 Post Function -

[MAG-II]

Issue #2 error message -

[MAG-II]

Issue #1 view screen, after error message -

[Fidel Castro Armario]

Hi @michaelgayheart,

Try using "Issue status (delayed writing)" as target field , instead of "Issue status".

[MAG-II]

Hi Fidel -

Issue status (delayed writing) configuration does not advance Issue #1 to the next step (Security Approved) when Issue #2 advances. With my current configuration (see below), it almost works. When I advance Issue #2 I get an error message, however, when I try to advance Issue #2 a second time then everything works.

So the second try with the transition does change the label of Issue #1 and advances Issue #1 to the next step, Security Approved. I remember months ago I had a similar problem, but I do not recall how we resolved it.

Any suggestions you may have would be greatly appreciated.

Post function configuration -

[MAG-II]

Post Function error -

[MAG-II]

Validator -

[MAG-II]

One more update -

I just tried the Issue status (delayed writing) when changing the Label name, and not the New Label name. This does seem to work after I refresh the page once. Do you think this is the best way to configure this kind of action?

I apologize for being so all over the place with this.

[Fidel Castro Armario]

Hi @hmichaelgayheart,

You can avoid the need for refresh by doing the following:

1. Use "Issue status" as target field, instead of "Issue status (delayed writing)"
2. Check option "Transition is triggered by a JIRA Workflow Toolbox post-function." at parameter "Skip validation when" in "Boolean validator with math, date-time or text-string terms", like shown in the screenshot:

[MAG-II]

YES. That totally worked. Thank you so much.

I am now having another annoying problem, although it's not a JWT problem. I created an additional workflow for this project. When making the workflow, for the first status, whatever I name that effects a different workflow, on a different JIRA project. I tried making copies of the workflow and renaming the first step, yet it sill effects a separate workflow on a different project. Is there a simple fix for this?

Again, thank you so much for solving my problem. This helps a lot. If you do have advice about my follow up workflow question that would be great. If not, no worries. Thanks!

[Fidel Castro Armario]

Hi @michaelgayheart,

The problem you describe is very strange. Try executing the JIRA Integrity Checker, available at Administration > System > .... Maybe, there is something wrong in your JIRA instance.

Otherwise, I think that you'd better create a support request to Atlassian.

[MAG-II]

Sounds good. As always, thanks for your help!

[Fidel Castro Armario]

We close the issue. Please, reopen it if you need to. Thanks.