Hi , is it possible to create following SLA using automation in Jira Software?

[MahanthPrudhvi]

Hi , is it possible to create following SLA using automation in Jira Software.

I (and few more fixed people) want to receive a mail after an issue has been created and if there is no transition happened for 24 hrs & 48 hrs.

I have created above using filter subscriptions and scheduled it but it is repeating the previously sent data as well.

Thanks.

[Kateryna_v_SaaSJet_]

Hi @MahanthPrudhvi 

It would be possible with the built-in SLA, such as in JSM, but for Jira Software, you can use only third-party add-ons. So if you are ok with apps, I suggest you try the SLA Time and Report add-on that was developed by my team.



You can configure SLA Start/Pause/Stop conditions and SLA goals as triggers for automation actions.

Use the 30-day trial period and just check this alternative solution.

[MahanthPrudhvi]

Hi @Kateryna_v_SaaSJet_ ,

Thanks for your suggestion. As I am not able to find any other solution that fits my requirement I am planning to  use your addon. I will start a trial version and if it fits good then I will go ahead with your addon.

[Kateryna_v_SaaSJet_]

@MahanthPrudhvi 
I will be happy if this solves your request. If you require any further assistance, don't hesitate to ask.

[MahanthPrudhvi]

Hi @Kateryna_v_SaaSJet_  I have tried this addon...it needs a bit more improvement.....but thanks for suggesting.

[Kateryna_v_SaaSJet_]

@MahanthPrudhvi 
We may already have cases of implementing the features you need using existing functionality, so we could show it visually at the One-to-One Live Demo. Book a convenient time, and we will be deeply grateful for your feedback.

Best regards,
Kateryna

[MahanthPrudhvi]

Hi @Kateryna_v_SaaSJet_ 

Thanks for writing back.....I have attended your addon's demo session and tried the addon and I felt it's not ready yet or not meeting my expectations so we have opted for another addon.

Regards,

Mahanth

[Bill Sheboy]

Hi @MahanthPrudhvi 

You seem to be describing sending an email report of issues meeting some criteria, and then for subsequent runs of that report, to not send the already reported issues.

If that is correct, and based on your criteria, you would need to some how update the issues to indicate they have already been reported upon.  Then your report can ignore them.  This could be done with a label, custom field, etc.

You could test this approach with your filter subscriptions by using the filter to bulk-update the issues to confirm they are not reported again.  If that works for you, you could implement both the email and the issue updates using an automation rule.

Kind regards,
Bill

[MahanthPrudhvi]

Hi,@Bill Sheboy 

Thanks for your suggestion.