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

How do you send workflow down a path based on entering a field?

Jonathan Harber

In my workflow, I have a point where a decision needs to be made. I have a field named Purchase Method. It has 2 possible options. RI and BRM. If the field is set to RI, there is one purchase path, if the field is BRM it follows a different purchase path. How do I achieve this?

It seems like a validator is the right answer

Accepted answers

All comments

Tony Rossiter

@Jonathan Harber

For what you're trying to do, I don' t think validators will work like you want it to. Conditions + Jira Suite Utilities would work better for this, provided that this field is set while in the status in which you want the decision point. They have a condition called Value Field that "Allows to execute a transition if the given value of a field is equal to a constant value, or simply set."

https://marketplace.atlassian.com/apps/5048/jsu-automation-suite-for-jira-workflows?hosting=server&tab=overview

FWIW, this is my most used workflow add-on. Well worth the money to license it.

Jonathan Harber

Tony, thanks for answering. This really is an If Then step. If the Purchase Method field is set to Option 1, send the request to Department 1 and use that workflow, notifications, etc., and if Purchase Method is set to Option 2, send the request to Department 2, and use that workflow, notifications, etc.

Will Conditions + Jira Suite Utilities do that? We have conditions installed.

Jonathan

Tony Rossiter

@Jonathan Harber

The short answer is: yes, you can do this type of conditional workflowing with Jira +JSU. Here's my similar use case:

We run an ITIL-based change management process through our Jira. As a public company, we also have to track and control changes to staging environments but only for SOX systems; all others just need prod changes tracked in scope. ITSO/ITSM approval is needed for any in-scope changes but how to capture both staging and prod approvals for just the SOX systems?

Solution: we created a SOX Yes/No field and required in on creation. In the workflow, SOX = Yes leads down one path, SOX = No leads down another:

sox yes no.jpg Essentially, depending on the value of SOX, the user can either to to "In Staging ITSO Review" or "In ITSO Review". The condition itself is mapped to the properties of my custom field, as detailed here:

https://confluence-apps.beecom.ch/display/JSU/Value+Field+Condition

Jonathan Harber

Right. So I'm guessing you have not come up with a way to do this without JSU Automation Suite?

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