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!


How does the portfolio 'sprints' report assign tickets to sprints?

From our project portfolio, accessing the report called 'sprints', on the story level, I can see a list of Sprints labeled 1-5 for our team with some of our stories split among each Sprint.

The thing is, none of this information matches our team's actual sprint information.

First, and most importantly, the tickets in no way line up to what we have completed or are currently working on. There are tickets showing up for previous dates that are actually still in the backlog, tickets that are displaying for an end date of a few weeks ago that are in the current open Sprint, and some showing for a sprint staring next week that are also in the current open Sprint. 

Second, our sprint naming convention is actually 18Q3S1 (for Sprint 1 of Quarter 3 in 2018), but the report is just showing random Sprint numbers that don't correlate to our actual sprints.

Third - least important and likely related, but worth mentioning - the dates don't line up with our sprints either. The sprints on the report run Tues-Mon, but we run Wed-Tues and we extended a sprint because of the 4th of July, which isn't reflected in these dates?

I couldn't find a way to configure it to show the correct data. Looks like the only configuration is for which attributes are shown for each ticket.

How is this reporting being populated? It seems like it would be really useful if it were correct, but it's so far off that it isn't helping much right now.

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events