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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

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
Dave Liao
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 19, 2020 • edited

@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
AUG Leaders

Atlassian Community Events