Hello,
I would like to create a time to resolution report and some questions:
-what is the difference between a resolution time report and the resolution time gadget. Are the results the same?
-We have created a dashboard with the TTR and are wondering why there are "Unresolved Issues" in the first column, there should only be Resolved Tickets in there, right?
-And in the list of tickets there are some that still have the status "Validation" or "Working"
-We suspect that this has something to do with the Resolved field, but we don't quite understand it yet. Who sets the status? For example, the status of the ticket is still "Validation" but the field is already "Resolved"? Created and resolved at the same time...Who sets this?
Thank you and best regards
Patrycja
Hi @Fabian Lim
thank you for your feedback. Could you please take a look at the board and the settings with my permission? I think this will be easiest, because unfortunately I'm still not sure where we should adjust the post function in the workflow.
Best regards
Patrycja
Resolutions are set to closed tickets and usually a prompt comes up asking you to set it. In other situations automation is used to automatically set it.
In your scenario, tickets are closed and the resolutions are set. However, the ticket can be pushed back and in most cases jira doesn't set the resolution field back to unresolved by default.
Here is a thread that explains more: https://community.atlassian.com/t5/Jira-Service-Management/What-is-the-difference-between-a-Resolution-and-a-Status-that-is/qaq-p/1202907
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Fabian Lim
thank you for your quick feedback.
But it's still not clear why does the first column of the diagram say "Unresolved tickets"? In the list are tickets which are Resolved.
And why the ticket from my scenario, which is also in the list, is Resolved, although the Resolved filed "Open" is?
-Resolved Filed is still "Open"
-Resolved date is the same as Created date - why is it so?
-According to the history, the ticket has not been pushed back, only the status has been changed.
Thank you
Patrycja
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It looks like there are some misconfigurations in your environment. For example, beside validation, you have a checkmark with open. This means that the ticket was resolved in jira terms.
You may have a workflow postfunction or automation that sets the created ticket with "Open" resolution. Which is being misused. Which makes sense with the dates and history you shared.
I hope this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Fabian Lim
could you please tell me where I can make the changes on the configurations to see what postfunction/ automation is set and change it?
Thank you and best regards
Patrycja
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Fabian Lim
Can you give me some feedback here? Unfortunately, I can't find a place in the settings where we can adjust the resolution field accordingly. Our workflow status looks like this:
When we create a ticket, the field "Resolution: Open" is automatically set. Only after we move the ticket into Validation, the field disappears.
Best regards
Patrycja
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You have to get to the postfunction of your workflow:
https://support.atlassian.com/jira-cloud-administration/docs/configure-advanced-issue-workflows/
You have to be a system admin to change this. Maybe that's why you can't get into the settings.
Also, is this a team managed or company managed project?
Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Fabian Lim
thank you for your feedback. Could you please take a look at the board and the settings with my permission? I think this will be easiest, because unfortunately I'm still not sure where we should adjust the post function in the workflow.
Regards
Patrycja
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you can't figure it out, contact atlassian support and they may be able to help you better. They may able to log in into your environment as well.
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.