Just wondering if bulk setup for work schedules is in the roadmap at all since this was raised back in 2021. This is intensive time-wise and if this needs to be done for every sprint, that's a lot time wasted on setting up something which essentially just needs to be set up once (with few updates throughout the year).
Same applies for setting same non-working days across Teams [all Developers have the same non-working days] - currently you have to update individually which across a large number of developers is an absolute pain in the ........and waste of valuable time
Use case from CraftJack: we should be able to save and edit schedules to assign to team members so that we save time in setting up schedules to be used for sprint planning purposes. Currently, we need to set schedules team member by team member, which creates redundant work for an Aha admin user. Potential schedules I might create would be: frontend developer (shared between teams), backend developer (one team), QA engineer (shared between teams), maybe junior / senior developer, and devs on issue tracker (fixing bugs instead of new dev for one sprint; rotates).
Just wondering if bulk setup for work schedules is in the roadmap at all since this was raised back in 2021. This is intensive time-wise and if this needs to be done for every sprint, that's a lot time wasted on setting up something which essentially just needs to be set up once (with few updates throughout the year).
Same applies for setting same non-working days across Teams [all Developers have the same non-working days] - currently you have to update individually which across a large number of developers is an absolute pain in the ........and waste of valuable time
Use case from CraftJack: we should be able to save and edit schedules to assign to team members so that we save time in setting up schedules to be used for sprint planning purposes. Currently, we need to set schedules team member by team member, which creates redundant work for an Aha admin user. Potential schedules I might create would be: frontend developer (shared between teams), backend developer (one team), QA engineer (shared between teams), maybe junior / senior developer, and devs on issue tracker (fixing bugs instead of new dev for one sprint; rotates).