JIRA scheduled job / service

[Alex Perez]

Hello,

I recently got an user requirement and don't know which approach is best, or if there is another solution i'm missing.

The requirement:

When a user opens a ticket and the L1 support asks for more information, the ticket is on "pending info" status. If the ticket is left in this status for 15 days or more, then "somehow" the ticket is closed.

In older Jira versions, some years ago, I implemented this by creating a transition that can be executed by a service user. This service user executes a JQL to find out what tickets are in status = X and not updated since 15d, then execute batch update.

Solutions:

a) implement a jira scheduled job

b) implement a jira service

c) others options ...?

scheduled jobs and services seem to be pretty the same thing, but services are able to start, stop, change scheduling and so on. scheduled jobs seem to be internal.

[Jack Brickey]

I would (and do) use an automation/scripting addon to automate the process. However, as you mentioned you could simply create a filter with subscription that runs daily and is sent to someone that then performs a bulk update.