I just created a Resolution Reason of "Stale" for tickets older than a year. I then added the resolution screen to the workflow (transition) when a ticket moves to closed. I then bulk changed all 320 tickets to closed with a resolution reason of "Stale" and now all of those tickets are appearing as closed with a resolution reason of "Fixed".
Even when I manually edit the resolution reason to "Stale" it saves as "Fixed. Why is this happening??
Is there a Post Function in your workflow transition that is setting the Resolution to Fixed? That would override a user entry in a transition screen.
Hello @Daniela Cardenas
It sounds like the Workflow for the issue is setting the Resolution field in a Post Function in the workflow transition to Done.
You said you added a transition, and that you are able to use the transition screen to indicate you want the Stale value for Resolution.
You need to go back to editing the Workflow transition where you added that transition screen.
The click on the Post Functions tab.
Look for an entry that is setting the Resolution field, similar to this:
If that exists, it needs to be removed. That Post Function is being executed after you complete the user interaction part of executing the transition, and it is over-writing the value you manually specified for the Resolution field.
To remove that post function hover your mouse over the far right area of that row. That should make a few options appear including the Delete option. Click the Delete option to remove the post function.
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.
I will check the project if a default resolution is set or you have some automation that sets this.
Look at the ticket history just to confirm what’s going on for example is the reason first set to stake and then fixed? This for me will hit at an automation somewhere.
Let me know your findings to the above
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi thank you for your reply.
No, I checked the history of the tickets, and I don't see the ticket changing from "Stale" to "Fixed". It's just changing to "Fixed" and there is no history of a "Stale" resolution reason on the ticket.
This project doesn't have any default resolution reasons that I can see.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
To narrow down what is going on here and rather than using bulk edit, can you manually transition one of the issues you had edited and set the resolution field and check what happens.
The behaviour above seems really odd.
Also check your workflow itself this is what shows if a default resolution is being set on the said transition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I had already tried to manually change a resolution and that, too, shows it as "Fixed" instead of "Stale" if I set it to "Stale.
I don't see any default resolutions either. No matter which resolution I try to set, it continues to default to "Fixed". It's super strange.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I tried to set to any other resolution type and no resolution type works. It defaults to "Fixed" no matter what I choose.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
In your workflow check if there’s a post function when performing this transition that sets the resolution field.
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.