I am trying to create a rule that when an sub-task, project, etc is transitioned from "in-progress" to "pending verification" if no activity then it will transition to Done. The issue I am having is I want it to wait a set amount of time (7 days) in the example below I am using 1 minute in test. As you may see it runs the rule after approximately 30 seconds. How do I ensure it will wait until the time set to trigger the action?
Welcome to the community!
Have you tried doing it on a schedule? It can check any tickets on a specific day say Monday's and Friday's where the it goes through and checks when the tickets were last updated and close out any that meet the JQL requirements you posted.
I'll keep working on trying to get it to work the way you want from your above image.
Let me know if you have any other questions.
-Brittany
Hi @Scott Howard Forbes -- Welcome to the Atlassian Community!
The two things you note seem to be contradictory:
As @Brittany Wispell notes, this may be better supported with a scheduled trigger, perhaps on JQL checking for a lack of updates in a time interval.
Would you please describe the problem you are trying to solve? Knowing that will provide context for the community to offer ideas. Thanks!
Best regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you @Brittany Wispell and @Bill Sheboy for replying to my question. I will take a look at the scheduler to see if that satisfies the intent. If I can run the scheduler and then have it JQL check for no updates for a week on "Pending Verification" issues that may work.
Bill, the issue we are having is Teams are placing sub tasks, projects, and bugs to "Pending verification" which then sit there never being verified by another party. I want to set up a rule that will close the tickets should this happen after a week of no updates to the item in "Pending Verification"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for clarifying, Scott. The scheduled-trigger rule looks like it could help.
Something else to consider: why are stakeholders not verifying those issues when they are ready? Are they too busy, do they find it unnecessary, have they moved on to other concerns, etc.? Having some quick chats with them may lead the team to improve your processes and understanding. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Fully agree with this Bill. Building this prompted me to see how many issues we have like this and seeing who the repeat offenders are. A good way to do a little analysis and have important conversations.
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.