Is it possible to create a transitional condition based on another transition?

[Eric Smith]

I am working on a workflow where I would like to make a transition conditional upon a ticket previously going through another transition. 

In the example below, the agent needs to jump between waiting for support and waiting for customer while they ensure they have all the information they need. This also pauses our SLA. When they have the information they need, they send the customer documentation to fill out using the "Send Docs" transition. Once the customer sends the documents back, I would like to transition from "Waiting for Customer" to "Validating Data" using the "Validate Data" transition. I would like "Validate Data" to only be presentable if the ticket has transitioned through "Send Docs". I have Script Runner and Jira Misc Workflow Extensions, but the closest conditions and validations are based on previous statuses, not transitions. They wont work in this scenario because the ticket will go through the same statuses. Any ideas how to make a condition or validation based off of previous transitions?

[Taranjeet Singh · Accepted solution]

@Eric Smith I would suggest to add a new Select List custom field, that acts like a flag, and set by default to "Yes" in the background when "Send Docs" transition is fired. Make sure this field should not be editable, once set.

Then, based on if the value of this custom field is set or not, you can create condition on "Validate Data" transition, based on which it will be visible or not visible.

Let me know if this helps !

[Eric Smith]

Thats a much more simple idea than I was conjuring in my head. Do you know if its possible to keep that field off of the screen but use its value in the condition? I know some of the default Jira stuff doesnt like to call fields that arent on a screen, but a groovy script might be able to. 

[Taranjeet Singh]

@Eric Smith To start with, You can use the new custom field, and set its value to "Yes" on a post-function of "Send Docs" transition. You can put this field on "Create" and "View" screens for the issue type or project but don't put this field on "Edit" screen for the issue type or project.

See if this approach works!