What we are building
Where Ganttry goes next.
The work already delivered, the problems in front of us now, and the directions we want to validate with Jira teams.
Last updated 29 September 2026
Recently shipped
Already in customers’ hands.
Marketplace release 2.24.0, published 29 September 2026: faster large charts, a new Workload panel and clearer planning menus.
- 01
Faster large charts
Large charts load much faster. Issues are read in parallel batches, and a real progress bar shows how many of the total have arrived.
- 02
Workload replaces Resources
A daily workload heatmap in story points, hours or percent, with a redesigned availability form.
- 03
Bulk changes on the Board
Mark rows with checkboxes and change status or assignee for all of them at once. Parent rows show a progress bar, and a Create issue row sits at the end of the Board.
- 04
A clearer Publish review
Filter by New, Later, Earlier or Selected and see how far each date moves. Publishing and undo are faster for large date changes.
- 05
Searchable planning menus
Redesigned status, assignee and row menus with search, avatars and the current value marked.
- 06
Late work at a glance
Late issues show how many days late they are, and violated dependencies are animated.
- 07
One timeline dock and clearer sprints
Today, scale, zoom, Fit and New note sit in one dock. Grouped by sprint, each sprint shows its state and dates, and the active sprint stands out.
Building now
A faster path to a trustworthy plan.
Our current focus: onboarding, useful starting points and verified workflows.
- 01
Deliberate timeline planning
Leave undated issues empty until a planner adds a one-day bar. Connect either end of task bars and keep dependency routes aligned during resizing. These changes are in implementation and verification, outside the production release listed above.
- 02
Guided first-plan onboarding
Guide a new user from choosing Jira work to understanding bars, dependencies, warnings, filters, scenarios, and publishing, so the first useful planning decision does not require learning the whole product first.
- 03
Built-in planning templates
Start from a practical setup for common work such as a product release, migration, campaign, or quarterly roadmap instead of configuring every view from scratch.
- 04
Focused stakeholder views
Give leaders and customers a concise, read-only view of dates, progress, releases, risks, forecasts, and decisions without exposing planning controls. Start with live views inside the customer's existing Jira and Confluence access boundaries.
- 05
Assistive-technology and scale verification
Verify complete planning workflows with current screen readers and real large Jira portfolios, remediate the findings, and keep measurable accessibility, responsiveness, and capacity evidence current.
Up next
Planning that travels beyond one screen.
The next notification, reporting and capacity workflows we intend to improve.
- 01
Proactive notifications and recipient rules
Build on the existing notification inbox with background evaluation, recipient rules, and supported delivery channels for critical work, release confidence, team overload, and approvals.
- 02
Configurable executive reporting
Let customers configure and save the measures, date range, grouping, and filters used by the existing executive and status reporting, then share a concise view of the decisions that matter to their organisation.
- 03
Calendar and leave integration pilot
Reduce duplicate capacity administration by synchronizing approved holidays, leave, and working patterns from one validated customer system while preserving Ganttry's identity, permission, and audit boundaries.
Exploring
Directions we are investigating.
Ideas that need more customer evidence before we commit to building them.
- 01
Clearer plan orientation
Keep source selection and the active planning context visible without copying the dense navigation used by larger planning suites. Preserve Jira keys and a readable hierarchy, keep Ganttry-only scheduling edits reversible, and require explicit confirmation for Jira writes. Saved views remain the primary way to preserve columns, grouping, filters, zoom, and table layout. Scenario context should become prominent only when the user has a meaningful alternative to the default plan.
- 02
Custom planning templates and workflows
Allow an organisation to define its own standard columns, grouping, calendars, reports, and review steps for new plans.
- 03
Supported integration and API access
Offer controlled access to planning results and supported operations for customer systems, with explicit permissions, bounded data, and an auditable history. Add specific Atlassian or third-party integrations only where they remove a demonstrated planning workflow gap.
- 04
Cross-site portfolio rollups
Bring selected plans from separate Jira sites into a higher-level portfolio for organisations that operate more than one Jira installation, when customer demand justifies the additional identity, residency, and administration model.
Help shape the roadmap