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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,559,517
Community Members
 
Community Events
184
Community Groups

Created VS Resolved Issue Report not showing the correct values

Hi Concern's


I am facing a challenge to get the correct data from created vs resolved issue report with in the given period of time.

As you can see that in below screenshot all the issues in report is showing against created whereas most of the issues have closed. 111.jpg




Please look  into this and do the needful.

Thanks

2 answers

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 09, 2023

Welcome to the Atlassian Community!

"Resolved" in Jira means that a resolution has been set on the issue (it can be any value, "unresolved" simply means there is a null/empty value in the database field).

Your graph tells me that your admins have neglected setting a resolution when your issues are closed.  They need to change your workflow so that it either asks a user to choose a resolution when they close an issue, or set it automatically with a post-function.  (And clear it on any form of "reopen")

0 votes
Marcin Wiktor
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.
May 08, 2023

Hello,

check if your issues are set with any "Resolution":
image.png

Maybe you messed something up with your workflow, and it does not set the resulution on transitioning to done statuses.

Hi Marcin,
Thanks for your response,

You are absolutely right, but the issue is to set Done status with accepted or closed to get the correct result in report.

Can you please guide how I can set resolution with status or workflow from setting in JSM?

Waiting for your kind response.

Thanks
 

Marcin Wiktor
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.
May 15, 2023

Sure, you can use this guide -> https://confluence.atlassian.com/jirakb/jira-issues-need-a-resolution-826873869.html

 

Then to update all existing issues, you can use the bulk change function to automatically set Resolution on the issues that are missing it.

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 15, 2023

Um, no, generally, in a correctly configured Jira, you can not use bulk change.

The reason for this is that the resolution field is never placed on an "edit" screen for an issue (nor create)

Bulk-edit will only offer you fields that are on the edit screen to amend.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events