How can I manage SLA in JIRA OnDemand?

[Paulo Gonçalves]

In my proof of concept I use a standalone version of JIRA+VertygoSLA. But now my companie wants to use JIRA OnDemand and this plugin is not available.

Is there another way to manage SLA on JIRA OnDemand?

Thanks!

[Renjith Pillai]

Tough, the closest possible way is to do the following:

• Use REST interfaces of OnDemand to query for issues (JQL) which have crossed SLA (or about to cross SLA based on your use case)
• If you want to avoid JQL, create and save a filter which has the conditions for the SLA
• Use REST interfaces itself to transition or comment on the issues (or take any appropriate action)

If running and external system is not feasible a semi manual way is to create the above filter and create subscriptions for those filters (daily) and someone needs to action upon those issue manually.

Erik's solution looks very interesting.

[Erik Westra]

We are now using Sladiator and developed an application that acts as a proxy: http://jira-to-sladiator.rhinofly.net/

[Erik Westra]

We have taken the application offline, we are now using Jira Service Desk. The source code can be found here: https://github.com/Rhinofly/JiraToSladiator

[Erik Westra]

I am wondering the same thing