Choose the work, set dates and connect dependencies. Give your team a shared view of what is planned, who is involved and when it could reach a release.
Plan your next releaseUse customer feedback, impact and effort to compare requests, bugs and improvements. Choose the work you are ready to schedule.
Put selected tasks on a timeline, set their dates and connect the work that depends on earlier tasks. Review the plan together before communicating a release target.
Customer feedback makes Custom roles a priority. The team reviews the linked backlog work, then plans access-model changes, the roles interface and release QA in Gantt.
┌─ REVIEW THE RELEASE PLAN ──────┐ │ scope Custom roles │ │ QA end Oct 30 │ │ target Nov 2 · planned │ ├────────────────────────────────┤ │ Team reviews the new window │ │ Share updated scope + timing │ │ Publish after actual release │ └────────────────────────────────┘
Organize customer requests and link them to backlog issues. Compare impact, effort and customer context in the scoring approach your team chooses.
In the sample Linear backlog, Custom roles is compared with SSO, an export fix and API refactoring. Your team reviews the ranking, revisits the effort estimate and chooses what belongs in the next delivery plan.
Priority does not assign dates or measure available capacity. Planning also needs the people involved, the work sequence and a realistic duration for each task.
Open Gantt chart in the Board or Report you want to plan. Find the work in Unscheduled Tasks, use filters or search, then drag selected tasks onto the timeline.
Move a bar to change its start and end dates while keeping duration. Resize its edges to change duration, or choose exact dates from the task’s context menu.
Keep Name and Score beside the timeline and add Assignee, Status or other useful fields. Group by assignee to review overlapping work; your team uses that view to check the plan.
Work you have not scheduled stays in the Unscheduled Tasks panel. You can unschedule a task when it no longer fits this plan.
The roles interface depends on the access model; release QA follows the interface. Choose Finish to Start for those scheduling constraints.
In the sample, access-model work extends from October 16 to October 20. The dependent interface and QA tasks shift; the team reviews a new November 2 release target.
Ducalis also supports Visual Links. They show relationships without enforcing dates. Create a link between tasks, then choose the dependency behavior and workday offset that fit the plan.
See scores, owners and statuses alongside the schedule. Choose the planning scope your team needs.
A Board’s Gantt contains tasks from that Board. Sort, filter and group them to review the next sprint, week or quarter.
Organize the timeline →Bring features, bugs and technical debt from the Boards included in your Report onto one timeline. Add tasks and dependencies for that plan separately: Board and Report Gantt charts are independent.
Plan across Boards →Synced tasks bring their configured name, assignee, status and other fields. Gantt start/end dates, duration and dependencies are managed in Ducalis; they do not sync to tracker date or blocker fields.
See what syncs with your tracker →Connect your task tracker → · Prioritize Jira issues → · Prioritize Linear issues →
Review the selected work, dependencies, owners and end dates together. If the sequence changes, update the plan and agree on the release window before communicating it.
Share a read-only Board link with stakeholders who need the Gantt, Backlog and Matrix views. Review the audience and visible information before sharing.
Use the public roadmap to show selected customer-facing ideas and their progress. Configure linked issue status rules separately; a Gantt bar or end date does not publish an idea or mark a feature released.
When the feature is available, review and approve its release announcement. Keep customer updates aligned with what has actually shipped.
Keep customers informed with a public roadmap → · Publish reviewed release notes →
┌─ REVIEW THE RELEASE PLAN ──────┐ │ scope Custom roles │ │ QA end Oct 30 │ │ target Nov 2 · planned │ ├────────────────────────────────┤ │ Team reviews the new window │ │ Share updated scope + timing │ │ Publish after actual release │ └────────────────────────────────┘
Use a story map and estimation criteria to decide which backlog items belong in a coherent release plan.
Choose a Board or Report, schedule a few selected tasks and add one real dependency. Review the timing and scope of your next release.
Plan your next releaseFollow the scheduling setup → · See the full feedback-to-release workflow →