nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Number of issues resolved counted multiple times

Paul Wiggers

Hello all,

Today I was made aware of the following situation and I am lost on how to solve this.

We would like service desk agents to resolve a minimum number of issues each day and discuss those numbers during our weekly meeting. This gives us a good idea of the workload, that problems the agents might have run into, etc.

To facilitate our customers as best as we can, we have a workflow which includes three resolving statuses.

Answer Provided
Resolved
Closed

We use automations to transfer an issue from 1 to 2 after a few days and from 2 to 3 after another few days. However, it turns out that the number of issues resolved is reported several times during those transitions.

So, an agent is "rewarded" when an issues moves into Answer Provided, again when the issues moves to Resolved and a third time when the issue is finally Closed. As you can imagine, this is giving warped statistics and we would like to see this resolved.

I am sure we are not the only ones using multiple resolving statuses and I am wondering how you handle the reporting of those issues?

Am I overlooking a setting? Is there another way to solve this?

Thanks in advance!

Accepted answers

All comments

Trudy P Claspill

Hello @Paul Wiggers

How are you getting the data that tells you the number of issues resolved per user per day?

When do you think the agent should get credit for the issue being resolved, based on the statuses you specified?

Paul Wiggers

Hello @Trudy P Claspill

I am using the default Atlassian reporting tools.

Some additional information to clarify before moving on. We have two In Progress statuses (Waiting for Agent and Waiting for Customer). The agent can only transfer issues to Answer Provided and/or Resolved (Calling them Resolving status from hereon). The Closed status is only available to the automation.

I believe the agent should get credit when an issue is moved from an In Progress status to a Resolving status. This means that when a customer replies that everything is ok the next day, the agent will receive double credit for the issue. This scenario is accepted.

However, what happens now is that, after a few days, when an issue with a Resolving status is moved to the next Resolving status by an automating, the agent is awarded credit.

Perhaps an example will help of what is happening now.

Agent legitimately resolves 10 issues on day 1 and goes on leave for a few days
- The agent is awarded 10 credits
On day 5, the automation transitions the issue from Answer Provided to Resolved
- The agent is awarded 10 credits
On day 7, another automation transitions the issue from Resolved to Closed
- The agent is awarded 10 credits

So, by resolving 10 issues, the agent is awarded 30 credits without the agent having to do any additional work.

I am looking for a way to award only 10 credits, even when the issue transitions from resolving status to resolving status.

Does this clear things up a bit?

Trudy P Claspill

How are you generating the report? Are you using a built in report? If so, which one? If you have built a custom report with your own JQL, what is that filter?

Paul Wiggers

We are using the built-in Tickets Resolved by Agent report. We don't (yet) use a custom report for this information.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management