Appearance
Roadmap
The roadmap is your list of projects and initiatives, and where you see what each one spent. Go to Delivery → Roadmap.
How the roadmap fits together
- Projects are what time and cost are recorded against. Effort from your project tool lands on a project, and capitalisation and R&D claims are built from projects.
- Initiatives group projects into one body of work and add up their forecast, actual cost and budget. An initiative has no cost of its own.
- Objectives say what the initiatives are for, with key results to measure progress. See Plan with objectives and key results.
A project doesn't have to be in an initiative. It still collects effort and cost; it's just flagged as having no initiative, so you can tidy it up.
You plan who works on the work on each project's Resourcing plan, and an initiative adds up its projects. How to divide work into projects is in Manage projects.
The tabs
| Tab | Use it to |
|---|---|
| Projects | Find and update a project, and fix projects with missing or wrong details. See Manage projects. |
| Initiatives | Group projects and track their forecast, actuals and budget together. See Group projects into initiatives. |
| Spend timeline | See each project's spend month by month, and spot spend outside its dates. See Track project spend by month. |
When a project tool is connected, there's also a tab named after it, such as Linear. See Your project tool's tab.
Objectives, and the initiatives under them, are in Portfolio, which doesn't have a tab. See Get to Portfolio.
To see whether a project delivered what it set out to, open its Value tab. See Project value.
Where projects come from
- Your project tool. Projects from Jira, Linear or Azure DevOps arrive with each sync. With Auto-create Flowstate projects on, each one becomes a Flowstate project, or is linked to one with the same name. With it off, you link them yourself on the tool's tab.
- Added in Flowstate with New Project, if your organisation allows it (Allow projects to be created in Flowstate, in Settings → Organisation → General).
- Imported, or added by your developers through the REST API.
A synced project only collects effort once it's linked to a Flowstate project. Until then, work on its tickets shows as Unattributed in the weekly effort report. See Fix unattributed effort.
Your project tool's tab
The tab named after your project tool lists every project synced from it, and the Flowstate project each one is linked to. Under each name are its dates, and the icon next to the name opens it in your tool.
| Column | What it shows |
|---|---|
| Status | The project's status in your tool |
| Owner | Who owns it in your tool |
| Creator | Who created it |
| Linked Project | The Flowstate project it's linked to, or Unlinked |
- Group by Linked Project (the default), AI Recommended, Status, Owner or None.
- Sort by Name, Status, Owner, Created (the default, newest first), Completed or Last Synced.
- Filter by Status, Owner, Creator or Link Status (Linked or Unlinked).
To link projects, or to have Flowstate suggest matches with AI Recommendations, see Link synced projects to Flowstate projects.
See a synced project's tickets
- On your tool's tab, select the project's row.
- Read the panel that opens. It lists the project's tickets, with each one's ID, Title, Assignee, Status, SP (story points) and Date.
- To narrow the list, select All, Active or Completed, or type in Search tasks....
Working in a scenario
If you change a project's dates or allocations inside a scenario, the change stays in that scenario until it's merged. Your live roadmap doesn't change. See Scenarios.