Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Get open/closed chart when project doesn't use Resolved status

We have 2 Jira projects for the same product. On one of them, we use the status fields as they were meant to be used. On the other, we have a custom workflow and all Jiras are resolved on creation according to Jira, but not to us.

I want to use the open v resolved chart on the dashboard, but it basically says that all issues were resolved as soon as they were created - which isn't helpful.

Is there a chart or report I can use on the dashboard to show the open/closed ratio?

To help you, here is the query I run to get items that are truly resolved in the first quarter:

(project = PROJ7 AND ("PROJ PT Product Docs (PD)" is not EMPTY) AND status in (closed, verified) AND status changed FROM "Product Docs" to "Verified" during (2020-01-01,2020-04-01)) OR (project = PROJ AND component = documentation AND status in (verified, closed, resolved) and resolutiondate >= 2020-01-01 and resolutiondate < 2020-04-01)

 

1 answer

1 accepted

1 vote
Answer accepted

@Nicole Baratta - hi Nicole! 👋

Check with a Jira admin (or with someone who has knowledge about why the project is wired the way it is) to see why issues are resolved upon creation. That's not typical behavior (of course), and naturally prevents you from using the best dashboard gadget for the job.

Depending on the answer, I'd generally recommend capturing the business definition of "Resolution" in a separate field (either a new or existing custom field).

A terrible* workaround would be to use the Issue Statistics gadget. It would show you the ratio, but only for a single moment in time (and it wouldn't be obvious for what moment in time that gadget is reporting on):

  • for the filter, save use the JQL you provided as a filter
  • use "Status" as the Statistic Type
  • set "Show Resolved Issue Statistics" as "Yes"

* figured I'd include it here to show you I put thought into this

Thanks! I was worried this would be the answer.  I have confirmed that it's actually not marking it resolved on creation, but when the status changes to 'Product Docs' which is when my work begins. I'm gonna check on why we're doing things this way and see if I can find a solution!

Like Dave Liao likes this

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Posted in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

4,243 views 12 5
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you