Resource Bandwith/ Capacity Planning

[Maeneth]

Hi Community,

Could you please assist me on the below?

•How to load whole scrum team capacity in Jira to use for sprint planning

•Visilibilty of available resource capacity while assigning new task to a resource

•Esimation lock post commitment – Resources wont be able to change the original estimation during the cources of the sprint.

Thanks you!

[Nataliya Vasyliv_Reliex_]

Hi @Maeneth 

I'm Nataliya from the ActivityTimeline team. Taking into consideration your requirements it seems like our add-on could fit your request. 

ActivityTimeline offers a features to help you plan out and schedule the workload for your team.

• Capacity planning: managers and team members can easily access important data related to their workload and capacity with the multi-functional indicator. The indicator is color-coded to help them become more productive and efficient.

• Availability: on the Workload indicator you can check resource availability instantly when scheduling the tasks.

• Cross-teams view: plugin delivers wide visualization in order for you to comprehend how to manage your teams more effectively. 
• Planning and org structure view: you can select multiple teams and schedule the tasks between users-teams in one timeline view.
• Accessibility: you can customize the settings of who can have the access to the system.

If you have any additional questions please feel free to ask me. We can provide a demo session for you if needed. Or read about more features here.
Best, Nataliya 

[Trudy Claspill]

Hello @Maeneth 

The Jira Software Cloud Standard plan does not include capacity planning features. To get capacity planning features you will need a third party application added to your system, or you will need to upgrade to the Premium plan and use the Advanced Roadmaps feature.

Jira Software Cloud does not include a feature to allow you to "lock" fields to prevent editing them. A work around for this is the disable the Edit permission for issues and then use a Workflow Transition and Workflow screen to present fields that are allowed to be edited.

You would use the jira.issue.editable property for every Status in your workflow to disable the editing of issues.

https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/

You would then create a screen with all the fields except the Time Tracking/Original Estimate field.

Make a new transition that loop back to the same status, and attach the screen to the transition. That will allow editing the issue without changing its Status, and allow you to control which fields can be edited.

https://community.atlassian.com/t5/Jira-articles/How-to-create-global-looping-transitions-in-a-Jira-workflow/ba-p/1135968