-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
14
-
When using the Classic Interface, It was possible to configure the days of the week that would be working days and the holidays, so when using the calculate Schedule option, the scheduled start and the scheduled end would consider the holiday and weekends when calculating.
Using the Improved Interface, we no longer have this functionality.
Use Case 1: Holiday
For instance, on this sample, the scheduled start and end had correctly skipped Saturday and Sunday ( Feb, 20 and 21) and the holiday (Feb 22nd):
The member "isabel@test.com" will work on 17th, 18th, 19th, and 23rd (32 hours, 8 hours per day):
When using the new improved interface, it is not more possible to configure weekends and holidays.
The autoschedule set the story estimated to 24 hours to be worked on 19th, 22th, 23rd (no way to skip the holiday)
Use Case 2: Working on Saturday
Using the Classic Interface, we can configure Saturday to be a working day:
The Story estimated on 32 hours will be worked on 18th, 19th, 20th, skip Sunday, skip Holiday and 23rd:
We do not have this possibility when using the Improved interface.
Workaround
The suggestion is to use the planned capacity that allows users to set and change sprint velocity for different sprints to reflect available members. This can be done for each sprint.
- relates to
-
JPOSERVER-2834 Configuring Non-Working Days in the Legacy Interface is not applied to Capacity in Chart
-
- Gathering Impact
-
- links to
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-25130] It is not possible to configure Non-Working Days using the improved interface
I agree this is a problem. I'm trying to make a roadmap where the resource is a machine park. The machine park should be allocated on weekends as well, but its not possible to configure.
please bring this back. If this is not part of the solution, the roadmap plan is basically useless for doing any planning. Its going to be purely for a team that doesn't care about capacity.
We've been trying to live with Roadmap without this function for 3 months now, and after 10 teams tried to adopt this, this has become a blocker to their requirement as this is the most basic stuff you need when planning stuff for your team.
this is clearly a critical feature. can we please get this fixed asap?
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