Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Created vs Resolved Dashboard not capturing tickets moved to my project

I was working on a JIRA dashboard i.e. Created vs Resolved for the last 7 days. But the issue is it won't pick up the tickets that are actually created 10 days back in a different project but moved to my JIRA project in the last 7 days. 

As it is moved to my project it is like a new ticket for my team so we would like to track that as a new ticket. 

Is there a way to the right output of Created vs Resolved tickets where:

1. Created shows all the tickets that are created in the last 7 days or moved to my JIRA project in the last 7 days. 

2. Resolved shows all the tickets that are resolved in the last 7 days or moved to a different JIRA project in the last 7 days.

1 answer

0 votes
Jack Community Leader Feb 25, 2021

Interesting. I have never run into this or at least never drilled down to understand that to be the case. However I don’t often move issues between project. I found this other thread - How-does-the-Created-vs-Resolved-Gadget-report-an-issue-that-has... . You will see that the accepted answer indicates the moved issues should include moved issues in the created. However given you observation I think that Ignacio’s suggested workaround might be warranted. Further I think it might be worthwhile checking Jira.atlassian.com for an existing suggestion on this and if not found report to Atlassian Support.  

Suggest an answer

Log in or Sign up to answer
TAGS

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