Complemento imprescindible de planificación de capacidad para Jira

Balance mode distributes a task's estimated hours evenly across all scheduled days, making it ideal for steady, ongoing work. Liquid mode front-loads the hours to fill each day up to the person's maximum capacity first, which is better suited for development tasks.

Yes, you can use Booking events to reserve time for general activities or Placeholder events for tentative future tasks. Approving a placeholder automatically creates and assigns the actual issue inside Jira, allowing you to plan headcount months in advance.

ActivityTimeline converts abstract Story Points into hours based on a customizable conversion factor defined globally or per project. To keep workload calculations accurate as time is logged, you should enable the option stating users do not log worked time.

Yes, you can hold Shift while dragging a task to split it, or use the "Split" button to divide estimates and dates among assignees. Alternatively, you can map a multi-user picker custom field to automatically create corresponding issue parts on everyone's timeline.

Time-off events automatically reduce a person's capacity and turn their timeline indicator blue, triggering an automatic workload recalculation for any overlapping tasks. Administrators can also use Holiday Schemes to apply country-specific public holidays to global teams automatically.

The Resource Utilization Forecast tracks weekly allocation, the Team Capacity Chart evaluates overall team commitments, and the Project Resources Forecast shows project time distribution via a heatmap. All of these reports export to Excel and can be added as gadgets to Jira dashboards.

The Users view displays individual timelines for exact day-to-day scheduling and availability checks. The Teams view aggregates collective capacity into a single row for high-level roadmap planning, keeping calculations accurate without duplicating tasks on individuals.

Jira issues sync automatically every 10 minutes, while any updates made directly inside ActivityTimeline sync back to Jira instantly. You can also trigger a manual refresh at any time or run a Full Synchronization for large configuration changes.

The system has seven permission roles ranging from Admins and Managers with global configuration access to Team Leads who manage specific teams. Regular and Limited Employees have restricted visibility, seeing either just their immediate teammates or strictly their own timelines.

Yes, issues assigned to active or planned Jira sprints with defined dates will populate the timeline automatically without manual scheduling. This works best when individual issue date fields are unmapped, though an advanced setting can force sprint dates to always take priority.

If your team only uses Story Points and does not log hours, you should disable time tracking to let the system spread the estimate evenly across the task's full duration. If you do log time, the default mode balances past worklogs with remaining future estimates for a real-time progress layout.

Yes, you can create non-Jira entries called Resources to represent contractors, rooms, or equipment and assign them specific skills or teams. While you cannot assign real Jira issues to them, they can be scheduled using Bookings and Placeholders up to your licensed user limit.