You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
I have rules that are triggered based on time, but I would need to create a rule that closes a ticket when a reporter transitions an issue to "resolved" without causing any conflicts.
For example, I have a rule that transitions a ticket to "resolved" when there's no response from the customer for 7 days and the status is "waiting for customer"; and then closes the ticket if there's no response for another 7 days and the status is "resolved".
Since I already have an automated rule that changes the status to "closed" after it's transitioned to "resolved" by the automation rule, I don't want that to conflict with another rule where the status is manually changed to "resolved" by the reporter. I want to close the ticket immediately if the reporter resolves the issue.
Any guidance is appreciated.
From what I am understanding, There shouldn't be any issues here.
For all of your automation rules moving the issue to Closed, it will only run this if it CAN. AKA, if it is in a status that CAN transition to closed, it will proceed. But since you are planning to move the ticket to Closed immediately after a manual resolution, it will already be in Closed, so those other automation rules will not run.
in addition to Amanda's input, you also have the ability to set a condition in your automation based on who transitions the issue, i.e. if a customer do "x" if not do "y".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Amanda Kirk and @Jack
To confirm, is my current setup correct? The time trigger rule will be ignored if the customer manually resolves an issue?
The customer "resolves" the issue.
System set "resolved" issue auto-closes ticket after 7 days of no response.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So by manual close you mean the user is transitioning the issue to close themselves (not automation doing it) correct?
If is already in Close because the user put it there then when these automation rules try to transition to Close it will see it's already in Close and not do it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.