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,456,998
Community Members
 
Community Events
176
Community Groups

Roadmap Sprints not reflecting the assigned story points

In the screenshot, we have a view of the current sprint, where every story assigned an estimate.  I don't see it reflected in this view. Am I missing something?Story Points.PNG

1 answer

1 accepted

0 votes
Answer accepted
Dave Atlassian Team Apr 28, 2021

Hi @Ahmed Saleh,

Could you confirm for me that the issues that have been given an estimate and assigned to the sprint have also been assigned to the Team associated with the board?

So the steps would be:

  1. From the sprint flyout in your screenshot click the "Filter issue by this sprint"
  2. Make sure that you are showing the "Teams" field in the fields section (use the "Fields" menu to add it if it isn't present)
  3. Check that all the issues assigned to the sprint are assigned to a team

If the issues aren't assigned to a team you'll need to make sure that you have a team associated with the board that the sprints come from. You can do this via the "Teams" tab... either create or edit an existing team and make sure that the team is associated with the appropriate issue source (i.e. the one that the sprints are on). Then go back and assign that team to those issues.

This should result in the capacity bar of the sprint accurately reflecting the assignement,

Regards,

Dave

Hi David,

Thanks for this.

As per your suggestions, I already have teams assigned. See the screenshot for more info.

teams assgined.PNG

I am unsure if our custom team field is affecting this. We have two team fields in our configuration:

  • Default team field: this one created  from the team tab
  • Custom field: the field that we use in our team sprints management.

Our board contains two sources: 

  • Board of the team
  • Filter

Thanks

Ahmed

Hi @David ,

I have been playing around with the board and it worked when I updated system fields story points and it wasn't working when a custom field that is specific to our project was updated.  The two fields are:

  • Story Points - system field 
  • Story points estimate - the custom field that we use in our projects.

My question:  Do we need to use the system field Story Points and change our projects, or there is a way to rely on our custom field that is already created?

Here is a screenshot of the board. story points system field.PNG


Like Dave likes this
Dave Atlassian Team Apr 29, 2021

Hi @Ahmed Saleh,

Thanks for the additional clarification of the problem. Yes, unfortunately you need to use the Story Points field for the estimate. Advanced Roadmaps is not configureable to use any other field for estimation (at least for points, if you configure your plan to use time based estimates then you can use the time logging fields within Jira - i.e. remaining estimate).

Regards,

Dave

@Dave Perhaps a future feature of Roadmaps would be an option to roll-up values from custom fields? That would be a very helpful feature for our team.

Like # people like this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events