-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Plans - Teams
-
None
-
1
-
Minor
Issue Summary
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Create a new Kanban project with sample issues.
- Create a new plan and linked to the kanban board.
- Change the plan view settings to group by "Teams" and flag the option "Show capacity on timeline"
- In "Teams" tab, edit the teams and put 300 capacity hours, so the issues will receive a floating number on their iteration capacity.
- Create a new Epic and link to a Team. Then, link to a story.
- You should see 37.5 per weekly planning.
- If you modify one of the weekly planning from 37.5 to 37 and submit the changes. It works.
- However, if I change it back to 37.5 is not possible anymore.
Expected Results
Based on the fact that team capacity can be measured using floating numbers, it should allow user manually change the duration iteration to a decimal numbers.
Actual Results
Team capacity does not accept the floating number for an individual weekly iteration after submit the changes. It simply ignores the new number and rollback to the previous one as soon as you click on the confirmation flag.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is cloned from
-
JSWSERVER-25996 Team capacity iteration duration does not accept floating number
-
- Gathering Impact
-
- relates to
-
JPO-31240 Loading...