-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
Feature request
Advanced Roadmaps for Jira (improved planning interface) renders the column for "Story points" with a fixed label. It does not reflect the actual name of the field.
This is a problem because it can misguide users on what the actual field name is:
- The default field is "Story Points" (with a capital P), not "Story points"
- There can be many "Story Points" style fields in Jira, including perhaps "Story points" (lower P), which is not the right field
- The true source of the field is opaque -> it is not documented, and the way to change it is obscure, requiring a database change
- Story Points field can be renamed to something else (in the event of instance consolidation, migration, other arbitrary reason).
- Boards can use multiple estimation fields, ARJ doesn't support this, rather it uses the JSW default
Suggested solution
Render the name of the column as the actual field name. This self-solves and guide the customer to the problem
- links to
- mentioned in
-
Page Failed to load
[JSWSERVER-25071] Render the "Story points" column name as the Jira field name
Dear all,
I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.
Sincerely,
Aakrity Tibrewal
Jira DC
So we have a planning roadmap, but we can't actually use it for planning. Brilliant.
Why is this a Suggestion and not a Bug.
THIS IS A MAJOR BUG IN YOUR PLANNING TOOL.
We are also experiencing this issue although it isn't even populating our data in those fields therefore we are unable to leverage the roadmapping tool to the fullest capabilities. When we add "Story Points" as a custom field in roadmaps the points populate.
My instance is running into this. Probably because of an ancient merge between two instances, and the "wrong" - seemingly identical - Story Points "custom" field having been chosen and used for some 20 years.
Would this issue also fix the problem where "Progress (story points)" on Plan roadmaps is not linked to the story points field that's used in the projects?