A few problems with Automation for Jira (SLAs and Transitions)

[Paul Richard]

In trying to work around a Service Desk Automation issue, I was trying to use Automation for Jira to transition on an SLA violation. However, I am observing a few things I would not expect :

1) I pick the "SLA threshold breached" trigger, but the "Select an SLA" drop down list contains 3 extra SLAs which do not exist. I believe they may have been deleted ages ago from when we were first experimenting with our setup.

2) When I pick the "Transition Issue" action and then the "Selecting a specific transition" the populated drop down does not provide all available transitions. We have multiple workflows with various transitions in each. I am seeing one or two from a workflow containing about ten. I also see most of the transitions on a second workflow, but none from the one I am interested in.

I don't get it, am I missing something obvious or are these known issues?

[Paul Richard · Accepted solution]

In case someone comes across this question, with respect to item (2), it turns out that the drop down is not fully populated with all transitions in the system. You must start typing the transition name and the list will filter down and the item will appear. In short, all transtions are all available, but the list only populates itself with a subset initially.

Item (1) (the extra SLAs) still appears to be a bug.