I have the following rule:
But it fails with:
Hello @hasancansaral
This sounds like your workflow does not allow a transition from Resolved, Closed or Canceled, back to Waiting for Support.
Could you share a screenshot of your workflow diagram?
In addition, it might be that the properties of the Resolved, Closed or Canceled issues, prevent you from editing the issue. Could you check if those statuses have properties set and if so, what properties?
The last option, is that there is a restriction on who can trigger the transition. Please check the Conditions of the transition in your workflow.
@Paul Wiggers Thank you for your response. I've updated the workflow and created a path from Resolved to Waiting for support. The rule now partially works, the issue status is transitioned to Waiting for support but it it not listed in Open issues. I thought that it may be because I'm not clearing its Resolution field and tried to clear it with:
But this time I get:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @hasancansaral
Good to hear that the transition is now working.
The easiest way to clear the resolution is to, once again, edit your workflow.
Select the transition > Select Post Functions on the right > add a post function > Clear Field Value > Select Resolution
That way, whenever the transition is used, the resolution will be cleared. You can then remove the action from the automation since the transition will take care of it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Paul Wiggers I've also managed to clear Resolution with Edit Issue action:
However, Transition issue to Waiting for support emails me every time. To overcome this, I removed Transition issue action and tried to add "status": "Waiting for support" to Edit issue fields. This time I got:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @hasancansaral
You can change that in the Notification scheme of the project or through your Personal settings, of course, the personal settings way is preferred so that your colleagues are still able to receive notifications.
Access your personal settings through your profile picture > Personal settings
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Paul Wiggers Thanks. I'm afraid that'd disable all notifications. I receive two in this rule, One from status change, one from the comments. I'd ideally receive only the email notification for the comment, since it has the same content with the Jira automation email.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, JSM can be quite notification heavy.
You can use the notification scheme to reduce some of them, otherwise, I'm afraid it is something you have to deal with.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @hasancansaral
Welcome to the Atlassian community!
Have you change to project to which this rule applies (the Rule Scope) since you set up the step to select the Waiting for Support status? If so, please try reselecting the status in that step. Or try deleting that step and re-adding it.
Do all the issues that might trigger this rule include in their Workflows a valid transition from Resolved, Closed, and Cancelled to Waiting for Support?
Who is the Actor for the Rule? Does the Actor have sufficient permissions to make that status change in that project?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Trudy Claspill Thank you for your response. I've successfully managed to transition the issue to Waiting for support, however, the issue is not listed in Open issues after being transitioned to Waiting for support. Could you look at my other comment?
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.