The Service Level Agreement - Your team is contractually obligated to respond to priority-critical issues within 48 hours. Run an RSE process every hour that will find critical issues that haven't been touched in 47 hours, and mark them as "Incredibly Important".
The Friendly Reminder - If a user is assigned to an issue and hasn't touched it in week, then it might be time for a gentle reminder. Have RSE check for this every day, and mark any issues it finds as "Needs Attention" (and send the assignee a polite-but-firm email).
The Spring Cleaner - Tell RSE to once a day look for any issues that haven't been touched in the last 6 months and close them out, since probably no one cares about them anymore. Much tidier!

Releases/Instructions

Check out our latest detailed notes for release 1.0.0 here . (They are still valid for the latest releases.)

Why RSE?

There are several ways to do automatic JIRA issue escalation! But only RSE is truly Really Simple. For example:

https://confluence.atlassian.com/display/JIRA/Automatic+Escalation+of+issuesjirakb/automatic-escalation-of-issues-612959361.html talks about Atlassian's official solution, which uses Jelly scripts - but, this means you have to write a Jelly script.
If you read https://confluence.atlassian.com/display/JIRA/Services, then you are half-way to rolling your own escalation service - but, then you still have to do the other half and actually write it.
Jamie Echlin's excellent and highly recommended Script Runner add-on includes functionality very similar to RSE, almost as an afterthought - but, it's a little hard to find the escalation part amidst all the other functionality.

...

Thanks for the feedback!!! https://e7solutionse7support.atlassian.net/servicedesk/browsecustomer/RSE/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel

Note: In order to provide any feedback, it is required that a User Account be created.

Image Removedportal/6