How does the Created vs Resolved Gadget report an issue that has been created in a project, but moved to another before being resolved?

Marc Pflieger February 17, 2016

We have a service desk which takes in issues that may be moved to another project after triage.  I was curious how the graph will represent those moved issues in its metrics?  Will it NOT register in both the created and resolved count?  or will it show in the created count, while not the resolved count?

2 answers

1 accepted

0 votes
Answer accepted
Udo Brand
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 17, 2016

It will show up in the graph for the project (or filter) where it currenty belongs to. So you could have this graph for two projects (a Filter with the one you moved from and the the one you moved to) and it will apear only once.

0 votes
Ignacio Pulgar
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 17, 2016

I would set the Created vs Resolved Gadget to use a filter instead of a project:

project = "Project A" OR (project = "Project B" AND Labels = "Project A")

Whenever you need to move an issue from project A to project B, edit it to add a label named "Project A" before moving it.

That way you will keep track of the issues created on project A that had been moved to project B.

Hope it helps.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events