nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Transition issue if it's on the same status for certain period of time

Jarrod Mochnick

Hi there, I had thought this was something pretty simple of out the box in Service Desk. Basically what we are trying to do is that if an issue is on the 'Resolved' status for 72h, it transitions to 'Closed' where it cannot be commented on and re-opened by a customer.

I swear I read how to do this and it was a simple automation step or part of the workflow. I guess I was wrong.

Is this possible without the need for the Automation for JIRA plugin?

Accepted answers

All comments

Mizan

I have implemented a similar scenario recently.

We have an SLA defined "Time to reopen" (We call it Time to answer) which breaches in 72 hours

This SLA starts when the issue reaches Resolved Status and ends when it is closed.

We configured a service desk Automation .

When Time to reopen breaches , Transition issue to Closed.

However, user can still comment.

So you do not need Automation add-on , There is automation feature which comes with JSD

Mizan

For disabling the comment , you can add workflow property on the Closed step of the workflow

https://confluence.atlassian.com/adminjiraserver071/workflow-properties-802592825.html

Jarrod Mochnick

Thanks Mizan!

I do have one question though - if the user re-opens the ticket, does the SLA timer restart? I would think that each time the ticket enters the Resolved status, the user should have 72 hours again.

Jack Brickey

yes. once it reaches the Resolved state again it will. simple test to prove it out.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-service-desk

transition

workflow

automation