I created a company-managed custom board (I'm the admin) to represent multiple projects in the same sprint. The backlog is not showing the Story Points on the issue row indicated by a dash or summed at the top of the sprint.
I have tried adding the field to the card layout but it doesn't occupy the Story Point field as expected. I also made sure the field was added to the screens and schemes.
Sound familiar to anyone? Thank you in advance!
Hello @Charisse Robison
You said this represents multiple "projects" in the same sprint. Do you mean the data is coming from multiple Jira Projects? If so, are al the source projects Company Managed Software projects?
Can you show an example of one of the issues that shows no story points in the backlog? Obscure confidential data. The part I am interested to see is the actual Story points field with its value.
The data is being pulled from multiple team-managed projects. The sprint board is created through a query I created to pull the project information in.
The attachment in the initial comment shows the data missing represented by the dash to the left of the priority symbol.
Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For a board created from a filter those estimate bubbles will reference only the native Story points field used in Company Managed projects. Team Managed projects use the Story points estimate field instead. Boards created from filters cannot reference that field in the Estimate bubbles.
The native Story points field is not supported in Team Managed projects.
So the only way to see the Story points estimate field value in this board is to add the field to the card layout.
There may be an open change request about this. I'll do a search to see if I can find one.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks again!
Good Points. I had already checked to make sure there were Story Point values on the issues. I can add the Story Point Estimate to the board, however, the story points don't display in the Story Point field. So your explanation about the difference in fields makes sense. Looking forward to the changes in the future.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, and...to Trudy's ideas:
There are several open suggestions to fix the "design choice" which created multiple story points fields in Jira, such as this one. You may watch / vote for it to see progress:
https://jira.atlassian.com/browse/JSWCLOUD-17173
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Trudy is at something here.
My guess is that the Story Point has no value, judging by the statuses having values. Verify that you can set a Story Point value for any of those issues.
if your project is Service Management project, those may not include Story Point field out of the box.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Charisse Robison , thank you for starting this thread!
I'm having the same issue here with a custom backlog consisting of multiple Team-managed software projects (with enabled estimation in story points).
The Estimation method for the board is configured to Story points, but there is no such field in the issue cards, and the "Story points estimate" from the stories is not displayed nor summed up on the board.
Can't wait for this disappointment to be resolved!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I guess the same thing with the Story point estimate field in the Team-managed projects is causing the issue with the Sprint Health Gadget on the Dashboard: it says "No estimated issues" while there are definitely stories with estimated story points in the sprint:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You are welcome. I appreciate the struggle. I also appreciate this might not have been a situation Atlassian thought of since it combines both company and team managed boards. However, it would be a great fix!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.