I want to automate our workflow and I don't know if this is possible on Jira.
After a task is moved from Progress to UAT we usually set 2 weeks as due date for our customer to give a feedback. Now, If in those 2 weeks we get no feedback I want the status to change automatically to Release, to extend the due date for one more week and to comment on the task @assigne please send an email to client and remind him about the feedback. If we don't get a feedback in this 1 week then task should be closed automatically as done. How to do this ?
Note:
I don't want this for all the tickets on UAT. I want it only with tickets that I set the due date 2 weeks, same for release 1 week.
Hi @Tomi,
Welcome to Atlassian Community!
This can be accomplished using automation. You can do that by creating an automation that runs on a schedule to check if the issue in the UAT status has been updated in the past two weeks, and if not transition the issue to Release. And you would create a second automation that would move it from Release to Closed if there are no updates in a week. The automation would look something like this:
Hi @Mikael Sandberg, thanks for getting back to me.
So my problem seems to be more big as it looks, I'll try to explain.
I want the automation to be only when I set the due date for exactly 2 weeks to the issue on UAT and 1 week on Release. Because there are some other tasks that I don't want to have the same workflow. For e.g. If I move an issue on UAT and I set the due date for 5 days I don't want to use this automation on that issue.
The automation I want is this: If UAT due date is changed to 2 weeks
then: If no update on the ticket for this timeline, move the issue to Release, change the due date to one more week and comment @ assigne please email the customer.
then: If no update on the ticket for this 1 week move the ticket to done and assign it to Project Manager.
Hope I was clear and I'm looking forward for your help :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So you would just have to use smart values in order to do that. You can use the automation I showed above and just add validation for the UAT due date that compares that to the current date. For the second step that requires a separate automation that runs based on the Release status and checks when the issue was last updated.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mikael Sandberg For testing it I tried it with less than five min but somehow It's not working. The smart vlaue for comparing due date with current date is
{{issue.duedate.compareTo(now)}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would use the diff instead, because the compareTo will only tell you which of the two dates are earlier. Something like this should do it:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, @Tomi ! As an alternative for this case, you can try to use the add-on Business Process Manager, developed by my team.
Using it, the program automatically moves issues through the workflow once core action is done. Also, you can create flexible due date
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Tomi, welcome to the community!
This seems possible through Jira Automation. Are you using Jira Cloud? Where does the customer give feedback, or how do you mark the issue when a customer gives feedback?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Garrett McCreery , It's the business analyst that It's supposed to update the ticket, if he doesn't receive any feedback from the client that means the ticket didn't have any update in those two weeks on UAT. Same is for the one week on Release.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.