Summary - Looking to restrict issues from a single project from being transitioned from one status to another for 24 hours.
More Color -
Team members are deploying requests (status = Deployed) and then immediately closing the ticket (status = Closed). Aside from being bad practice this results in others providing feedback on the deployed ticket causing the ticket to be reopened.
So I'm looking for a way to prevent the transition to Closed from happening for 24 hours past the time it was deployed.
I put the transition time in a custom field but I cannot figure out the scripting portion for the workflow transition to use.
Any/all help is appreciated.
Hi @Ron Lindstrom , While your requirement is tricky it is equally complex. If I were you, I would make it less complex, by restricting the close transition and limiting the project lead to perform a bulk update the next day.
Another solution that I could think of is to automate transition issues using restapi script.
Thanks for the response. Neither of those are what I'm hoping to achieve sadly.
Anybody can transition the ticket to Closed, I just want to make sure the previous status has been there for 24 hours first.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.