Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Conditional Execution Post Function not being recognized

Ryan Thomas
Contributor
March 10, 2017

I recently added JMWE to our Atlassian Cloud instance.

I have a test workflow to check for resolution as a condition to copy a field value using the basic description:

Update parameters of the Copy value from field to field (JMWE add-on) Function for this transition.


Copy Assignee to a Custom field.
This works normally.

Then I add this condition:

{% if issue.fields.resolution.name == "Fixed" %}
    true

And the Post Function is no longer functioning. This leads me to believe my resolution field reference is failing, but I'm not sure. 

Any one else fail with this basic task? 

 

1 answer

0 votes
Niclas Sandstroem
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 11, 2017

Do you set he resolution before you enter this condition? The code looks good but is this done after the post-function that sets it to Fixed? Else only thing I can think of is that you don't have that Resolution.

Suggest an answer

Log in or Sign up to answer
TAGS
atlassian, jira product discovery, product operations, product ops, linkedin live, atlassian events, cross-functional collaboration, product management, engineering collaboration, design collaboration, atlassian learning, agile teams, product strategy

Product Ops Unpacked: 4️⃣ tips every product pro needs to know ✍️

Join PM Evangelist, Axel Sooriah, & Product Ops. Consultant & Advisor, Jenny Wanger, as they unpack the role of product ops and discuss key takeaways in Atlassian’s ‘The Product Ops Mission’ guide. They’ll answer your questions live on May 6 at 9:00am PT.

Register here ⬇️
AUG Leaders

Atlassian Community Events