-
Suggestion
-
Resolution: Unresolved
-
423
-
159
-
Summary
By default and part of the rollout for the Estimation for Next-Gen projects, Jira now has two Story Points field.
- Story Points (company-managed)
- Story points estimate (team-managed)
id | customfieldtypekey | cfname |
---|---|---|
10015 | com.atlassian.jira.plugin.system.customfieldtypes:float | Story point estimate |
10021 | com.atlassian.jira.plugin.system.customfieldtypes:float | Story Points |
The default field that is used by Jira classic projects is the field Story Points.
If you, when using the Jira old view, add the Story point estimate (Next-Gen estimation) field and assign the number for the story point, this field does not work and the number is not displayed on the cards or at the new issue view or in the reports.
Steps to Replicate
- Click on Jira Icon on the top left corner > Jira Settings > Issues
- On the left side-bar, click on Screen.
- At the bottom of the field lists, enter "Story" on the field selection.
Expected behavior
As the new field is exclusive for Next-Gens projects, it is necessary to block this field usage to prevent miss assignments or miss usage of this field, blocking its usage in classic projects.
Actual behavior
On the board, the assign number for story point isn't rendered:
In Report View, the story point will display as null value:
Workaround
Assign the field "Story Point" instead of "Story Point Estimate" on Classic project's screen.
- is duplicated by
-
JSWCLOUD-17152 As a user, I only want 1 story points field, shared between classic and next-gen
- Closed
- relates to
-
JRACLOUD-71704 As a Jira Software user, I want to see the story points described as "Story points" in the new issue view
- Closed
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...