Amir Katz (Outseer) Expert

Thanks to@Gezim Shehu [Communardo] for pointing the direction. Here is the complete solution: In my project, I have two issue types, Incident and Service Request. Each one is associated with its own Field Configuration Scheme. Multiple request types are mapped to each issue type. In each field configuration scheme, choose…

Thanks to @Thanos Batagiannis _Adaptavist_ @Aidan Derossett [Adaptavist] - it works. I made a minor modification so that the field name is a constant that can be used more than once: import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.MutableIssue import…

I tried it in a workflow transition validator (using the option 'Simple scripted validator') and it does not seem to work. I read in another post that since Jira 5.x, the values are returned as a map, so they suggested this check: cfValues.get("customfield_17637")?.keySet()?.size() == 2 but it does not work for me (meaning…

What I actually did is this (sounds complicated, but it's not): * Created the two custom fields * Created a CSV file for System Import for first field (Customer Name) * Performed a system import, specifying the first custom field, which generates a dummy issue (with key=PROJ-1), and adds all 140 values to the custom field…

Yes, I did. All the associations are there. Please see screenshot:

It can be done in Diagram mode as well. However, you must check the 'Show transition labels' checkbox. Then you can click on the transition name instead of the arrow and choose the desired transition.

Edit the workflow in text mode

Yes they are. And I cannot do what you say - if I try to move the connection point, the editor creates a new transition. But there is a much simpler solution which just occurred to me, and it works - edit the workflow in Text mode instead of Diagram. 

No apology needed - you did provide a great tip about the status names, so I will use that. And I will rename the customer-visible transitions to be customer-friendly...

Jamie, thanks. That's a good solution. However, I realized that what I asked for is how to display the transition name in a customer-friendly manner, while you explained how to display the status. I'm looking at the Update Workflow Transition screen and there is only the Transition Name editable field, but there is no…

Good explanation. I assume the guidelines apply to core Jira and to Jira Service Desk, correct?

Thanks, Steve, but this is the answer I did not want to hear :-( Your suggestion is a acceptable workaround. However, the problem with condition-based routing is that the conditions are not shown in the workflow diagram, so one has to read the textual definition of the workflow. From a simple flow diagram, it becomes a…