Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Reports link continually taking me to previously closed Sprint Report

Brett McMillan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 20, 2020

When I click on the Reports link and navigate to that page, my default Report is the Sprint Report.  When I land on that Sprint Report, however, it keeps taking me to the last, previously closed sprint.  Obviously it only takes a second to click on the Active Sprint, but, why is this constantly doing this?  For more information, that last sprint was closed last Tuesday (8/11) and it still brings up the closed Sprint over a week later (8/20 currently).  Very strange...

1 answer

1 accepted

0 votes
Answer accepted
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 20, 2020

Hi Brett, welcome to the Community. Indeed that is what it defaults to. TBH, I have never given much thought as to the why. However, for me the reports section is where I go to look at history. I use dashboards and the scrum board itself to focus on the active sprint. With the dashboard I can include the active sprint burndown. 

Brett McMillan
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 21, 2020

I guess I would expect that page would automatically navigate to the last selected report automatically...

 

Regardless, I was not aware that Sprint Burndown gadget existed!  I've added that to my dashboard and that pretty much solves my problem!  :) 

 

Thank you!!

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 21, 2020

Hi again Brett. I found this issue - JSWCLOUD-13715 reported as a bug. It was closed as "won't fix" but I found the comment a bit odd TBH. Sort of a mix between 'no one is showing interest' and 'cannot reproduce'. You might do any/all of the following:

  • click the feedback and give Atlassian feedback on your preference
  • add a comment to the above JAC ticket in hopes someone will reopen/respond
  • open a support ticket w/ Atlassian Support

IMO, the best option to get a response is the last one.

Like Brett McMillan likes this

Suggest an answer

Log in or Sign up to answer