Roadmap & calendar
The roadmap timeline, the calendar of due dates, initiatives, project milestones, releases, and the optional Plans module for cross-project planning.
Roadmap
More → Roadmap draws a project’s epics on a timeline. Choose the project, then:
- Switch between Timeline and Table views, and zoom the timeline by Weeks, Months or Quarters. The Today line shows where you are.
- Each epic is a bar from its start date to its due date, with its progress. Child issues are listed under it.
- Drag a bar to reschedule it, or drag its ends to change the dates.
- Releases and Milestones appear on their own rows as markers, coloured for open, overdue and reached.
- Dependencies (starts before / finishes before, blocks) are drawn as arrows between bars; Schedule conflicts above the chart lists dates that contradict a dependency. See Links & subtasks.
If a project has no epics, the roadmap says so — create an epic and give it dates.
Calendar
More → Calendar shows issues by due date on a month grid. Use the arrows to move between months and click an issue to open it. For other date fields (start, created, updated) build a view with the calendar layout.
Initiatives
An initiative groups epics and whole projects into one goal that spans teams. Open Projects → Initiatives.
- Press New initiative, enter a name and optionally a description, Start date and Target date (the target cannot be before the start). You become the owner.
- On the next page choose Link epic (add an epic by its key) and Link project. Linking a project includes all its issues; linking an epic includes its children. The same epic or project can belong to several initiatives.
- The detail page shows overall Progress, progress per epic and per project, and a timeline strip (“15 days left”, “5 days past the target”).
Status is one of planned, active, completed or cancelled. Post a health update — On track, At risk or Off track, with a note — to tell stakeholders how it is going; the latest shows as a badge and the history is kept.
Milestones
A milestone is a named target date inside a project (“Beta”, “Public launch”) that issues are attached to. Project administrators create them on the project page; anyone who can edit an issue can add it to a milestone through the issue’s Milestones field (hidden if the project has none). A milestone is open, reached, or flagged overdue if its date has passed. Only issues of the same project can be attached. Search with JQL: milestone = "Beta", milestone is EMPTY.
Releases
Each project has a Releases page: its versions, newest first, with progress, issues still open, an overdue flag and release notes grouped by issue type (copy them as Markdown). A project administrator presses Mark released; Veqsio warns if issues are not done and fills today’s date if none was set. Details on versions are in Projects & templates.
Plans (Enterprise module)
Plans add planning across projects — what many teams use instead of a spreadsheet:
- A plan collects projects, boards and saved filters. You only add what you can see, and everyone sees the plan through their own permissions.
- A configurable hierarchy above the epic with roll-ups of dates, progress and estimates.
- A timeline with sprints as bands, releases as milestones, dependency arrows and drag-to-reschedule.
- Teams and capacity: weekly capacity per person against assigned load, with over-allocation highlighted.
- Scenarios: try changes in a draft, compare with the baseline and apply them to the real issues, with a result for every issue.
Plans need a licence that includes the module; without one the entry is hidden.