Introduction to Taskstreamer
Understand the core concepts behind the first self-updating roadmap and how it transforms product planning.
Can't find what you're looking for?
Our team is here to help you get the most out of Taskstreamer
From first steps to deep technical documentation:
everything you need to get going with Taskstreamer.
Found 0 results for ""
Try adjusting your search terms or browse the categories below
Deep-dive into every feature, configuration option, and best practice
Everything you need to go from zero to your first auto-updating roadmap
Understand the core concepts behind the first self-updating roadmap and how it transforms product planning.
Understand what way of working Taskstreamer supports enabling project- and Agile thinking including frameworks like Scrum, SAFe, Waterfall and more.
From your invitation e-mail to your first Thread on the sprint board in five steps: sign in, find your way, create, work on and plan a Thread.
Get your first roadmap running in under 10 minutes. Connect Jira, import features, and see automatic scheduling in action.
Navigate the dashboard, understand views, and learn keyboard shortcuts that power users love.
Step-by-step guides for every deployment scenario
Nothing to install: what an administrator sets up first, in order: sign-in, Workspaces and Teams, Projects and file shares, people and roles, planning and AI.
Install Taskstreamer from the Atlassian Marketplace and configure for Jira Cloud in minutes.
Deploy Taskstreamer on your Data Center infrastructure with clustering support and enterprise security.
Deploy the standalone Strategy application for OGSM planning that connects to your Jira instance.
Who the guide is for, and the words Conductor uses: Workspace, Value Group, Team, Project, Module, Thread, Feature and Sprint.
This guide explains how to work with Taskstreamer Conductor by hand, the way you would use a ticket and planning tool such as Jira.
What Workspace, Value Group, Team, Project, Module, Thread, Feature, Sprint and the Operations board mean in Conductor.
The screenshots were made in Taskstreamer's demo organisation with AI switched off, as a new organisation starts.
Set your password, sign in with a password, an e-mail code or your organisation's account (SSO), and reset a forgotten password.
You never receive a password from Conductor. When an administrator invites you, you receive an e-mail with the subject "[organisation] has invited you to Taskstreamer".
The Remember me box on the sign-in page has no effect at the moment. A session stays open while you work: Conductor renews it in the background for up to 7 days.
When your administrator has switched on Require email code at sign-in, every sign-in with a password asks for a code.
When your organisation has connected its identity provider (for example Microsoft Entra ID, Okta or another SAML 2.0 or OpenID Connect provider), the sign-in page shows…
At most 3 reset mails are sent per address in 15 minutes. While SSO is enforced, a password reset is not possible.
Open the user menu (your initials at the top right) and click Sign out.
The user menu, your language, e-mail about Threads you watch, changing your password, and your own data and privacy.
Your initials at the top right open My profile, Change password, Your data and privacy, and Sign out.
Screens, e-mails and notifications then use this language. If you choose none, Conductor uses your organisation's language, then your browser's, then English.
On My profile, the box Email me about threads I watch decides whether notifications also come by e-mail.
Change your password and sign out on all your other devices at once. This browser stays signed in.
Download my data gives you a file with everything Conductor holds about you: your profile, the Threads, comments and history you are part of, and your planning data in…
Workspaces, Value Groups and Teams, Team members, the states of a Team's workflow, and the Operations board setting.
Open Workspace, then Settings. The first tab lists the Workspaces. Editing needs workspaces.edit, deleting needs workspaces.delete.
Open Workspace, then Value Groups. Each Value Group lists its Teams. To create a Team, click New Team in a Value Group (permission blueprint.admin.manageTeams).
Open Team, then Members. You add and remove members, set each member's role in this Team and their availability.
Open Team, Settings, tab Workflow. Every Thread is in one of the Team's states.
Open Team, Settings, tab Operations board. A municipality often works without sprints; this board is for that.
The Team dashboard shows the current sprint, its Threads, the velocity of earlier sprints, the Team's Projects and members, and the Team's capacity.
On the Members page you choose the Team's owner, give each member a role in this Team and set what the AI may do for the Team.
Availability says how much of their time each member has for a sprint; the Capacity section compares the Blueprint plan with the Threads booked in the sprint.
The Team settings also let you rename words for this Team only, and decide whether a Thread may be closed while acceptance criteria are still open.
The Workspace dashboard shows one Workspace at a glance: its Threads, its Projects, what waits for your approval and, with the right permission, delivery figures.
The Workspaces tab lists every Workspace with its figures; editing a Workspace changes its name, its domain and its Guardrail tabs.
A Value Group groups Teams that share one priority list; you create, edit and delete Value Groups on the Value Groups page or tab.
On a Labels tab you rename the words Conductor shows, such as Project or Sprint, for one Workspace, Value Group, Project or Module.
The Phases tab holds the ordered set of phases that the Threads of a Workspace run through, and the controls on those phases.
The Products/Services tab holds the products and services that Blueprint uses for a Workspace, each linked to one or more Value Groups.
Two tabs shape how Initiatives work in a Workspace: Templates adds fields to the Initiative form, Refinement sets up the refinement board.
The Iterations tab holds the calendar Blueprint plans with: the PIs of the Workspace and their Sprints, and the own Sprint cadence of Teams that do not plan in PIs.
A value bucket model scores the value of work on several weighted buckets; you build models and assign one to each Value Group.
Projects, and Modules that say where their work and files go: a repository, a file share, or nowhere.
Open Workspace, then Projects, and click New Project (permission projects.create).
Open Project, then Modules, and click Add Module (permission projects.edit).
The Modules page of a Project lists its Modules, where each one stores its work and which Team it belongs to.
The Module page brings together everything about one Module: its work, its Guardrails, its output and its discussion.
The Overview tab shows what a Module is and how its work stands, in figures and short lists.
The Repository box on a Module's Overview shows where its work is stored, and lets you point the Module at another repository, folder or branch.
The Commands box on a Module's Overview names the commands for testing, linting, building, formatting and installing the Module's code.
The Output tab shows the files or code a Module stores, and the Discussion tab holds comments about the Module.
Each Module has its own AI switch; AI only runs on a Module's Threads when the organisation, the Team and the Module all have AI on.
You see your Projects on the Projects page and manage all of them, archived ones included, on the Projects tab of the Workspace settings.
You edit a Project's name, Workspace, type, description and base branch; its key is fixed when you create it.
The Project dashboard shows the state of one Project: its Milestones, its open and flagged Threads, its current Features, its Teams and its repositories.
The Project settings hold the Project's system connections, the location of each Module's code, the Project's own words and its AI models.
The rules every Team's work must follow: Guardrail types per Workspace, the Project's and each Module's Guardrails, gaps and the graph.
Guardrails are the written rules for the work in a Project, grouped by type, such as architecture, security or testing, that people and AI must follow.
An administrator of a Workspace chooses which Guardrail types its Projects use, in which order and under which name.
The Guardrails page of a Project holds one tab per Guardrail type, where you write the rules that apply to all work in the Project.
A Module can add its own Guardrails per type, for rules that apply only to its work; the Project's Guardrails always apply as well.
A gap is a weak spot found in the Guardrails, such as a weakened rule or a contradiction; you resolve it, dismiss it, or open a Thread to fix it.
The Graph tab on a Project's Guardrails page draws every rule of the Guardrail index and what each rule applies to.
Guardrails apply to every Thread of the Project, and a Thread's Module adds its own; with AI on, the AI gets these rules for each step.
Milestones of a Project: create and edit them, how their status is worked out, and the progress report.
A Milestone is a dated delivery goal of a Project; it follows the Features of the Initiatives you link to it.
Conductor works out a Milestone's status from the planned end dates of its Features; you can override it with a reason.
The progress report is a versioned one-page status of a Milestone, written by its owner: five statuses, short texts and the live list of deliverables.
Create and plan Features, the Feature page, states, block and postpone, Teams, estimates and dependencies, and deleting a Feature.
A Team and a Project each have a Features screen: a timeline of their Features, planned per sprint in Blueprint, from which you open each Feature.
You create a Feature from a Team's Feature plan; it starts in Ideation and is created in Blueprint too.
The Feature page holds the Feature's description, acceptance criteria and Threads, and on the right its planning and details.
A Feature moves through eight states; you move it forward with one button, and block or postpone it with a reason and a date.
In the Planning box of a Feature page you choose the Teams that deliver the Feature, their estimate in sprints and share in percent, and what the Feature waits for.
You delete a Feature from the More actions menu on its page; a Feature that still has Threads cannot be deleted.
Create a Thread, and work with priority, team rank, labels, due dates, watchers, comments, the Thread list, filters and CSV export.
The Thread gets a key: the Project key, a dash and the next number, for example IT-12.
Click a Thread to open it. The address is /threads/<key>, for example /threads/IT-4, so you can share it.
A Thread's priority comes from its Feature's place in the Value Group's priority list in Blueprint: the first Feature gives P1.
The Team rank is the Team's own order of its Threads, numbered from 1.
Labels are the same for the whole organisation.
Pick a date in Due date, or click Clear to remove it. The Thread then shows "Due [date]", or "Overdue: due [date]" when the date has passed.
Click Watch to follow a Thread, Stop watching to stop. You can only add or remove yourself.
Open the tab Discussion, write in the editor and click Send. Type @ and a few letters of a name to mention someone.
Delete thread at the bottom of the right column archives the Thread (permission threads.delete).
Team, Threads lists the Team's Threads, grouped by Feature in priority order.
The Context row of a Thread page shows its Project, Team, sprint or Operations board, and Feature; there you fill in what is missing and plan the Thread.
A dependency says that a Thread waits for another Thread of the same Project; the Thread cannot move on until that one is Done.
The sprint board, the Operations board, moving cards between states, and planning sprints.
Team, then the sprint board, shows the active sprint with one column per Team state.
When the Team uses it, Team, then the Operations board, shows the Threads that are not in a sprint, in the same columns.
With the mouse: drag a card to another column or another place. A column your role may not move into shows the reason, and nothing is changed.
Team, Sprints shows the sprints of the Team.
The Sprints page shows five sprints of the Team side by side, each with its Threads and points, and is where you open a sprint.
On a sprint's board page you add Threads to the sprint, take them out, set the sprint goal and the members' availability.
Starting a sprint makes it the Team's active sprint and records which Threads and points were planned at that moment.
Closing a sprint records its figures, retrospective and velocity and ends it; Threads that are not finished stay in the closed sprint until you plan them again.
The sprint's page shows the sprint's points, predicted velocity and availability, and once it is closed its retrospective and the outcome of each Thread.
The Sprint board and the Operations board show one column per visible Team state, with compact cards that you filter, expand, size and assign.
A Thread goes onto the Operations board when it is created there or planned there from its page; Done cards leave the board after the Team's retention period.
Where files are stored, which files are allowed, size limits, the virus scan, and what happens when a file cannot be attached.
Files attached to a Thread go to the file share of the Thread's Module, never into Conductor, in a folder per Thread.
Drag files onto a Thread's Attachments box, follow the upload and check, and see the share and limits that apply.
Text files must be UTF-8. Files ending in .txt, .csv and .log may also be Windows-1252.
The administrator sets the limits per file share connection (see “Attachment limits per connection”), between 64 KB and 100 MB per file.
Every file is scanned for malware after the checks above and before it is written to the share.
Characters that Windows does not allow (< > : " / \ | ? *) become _. Leading and trailing dots and spaces are removed.
Click the download button next to a file to download it.
The messages you see when a Thread's Module has no file share, or its connection is missing or unreachable.
Initiatives on the roadmap, the refinement board, priorities, the feature plan and the connection to Strategy.
Blueprint is Taskstreamer's planning system. Conductor shows its planning screens on the Workspace tab and reads and writes Blueprint directly.
The refinement board (its name is set in Blueprint, for example "Initiative Refinement") is a board on which Initiatives move towards ready.
Priorities is the Value Group's priority list of Features. This list is what gives Threads their priority (see “Priority”).
Feature plan (Workspace) shows all Teams of the Value Group on one timeline.
When your organisation also uses Taskstreamer Strategy, an administrator connects it under Administrator, License, section Strategy App Integration, with the Strategy…
Every planning screen works on one Value Group that you pick in the side bar, and a Value Group lives in Blueprint as well as in Conductor.
The roadmap shows the Initiatives of the Value Group as bars over quarters, with one row per Product/Service, and you can drag a bar's edges to change its quarters.
An Initiative has a title, a Product/Service, a timeline in quarters, a status and optional predecessors, and you set them in one form.
The detail panel shows everything about one Initiative in four tabs, and lets you edit its texts and template fields or delete it.
The Feature Map tab shows the Initiative's Features in columns by end quarter, where you create and link Features, draw dependencies and finalize the plan.
The refinement board moves Initiatives through five columns towards ready, and each card carries a checklist of actions with assignees and due dates.
The priority list shows which Teams work on each Feature, previews new end dates while you reorder, and saves the order to Blueprint, which then recalculates the plan.
A challenge says that one Feature or Initiative should rank above another, and a person who resolves challenges decides it, with help from the Value Group's value model.
The Feature plan shows each Team's work on each Feature as a bar over the sprints, with its status, dependencies, locks and pauses.
Blueprint calculates the Feature plan from the priorities, each Team's estimate and share, the dependencies and the sprints; Conductor refreshes it every 20 seconds.
A Team reports its progress in the Feature plan, and a whole Feature is blocked or postponed on its page; Blueprint uses both in the next calculation.
The Team dashboard compares what Blueprint planned for a Team in a sprint with what the Team booked in Threads, and lets you set each member's availability.
When Blueprint cannot be reached or refuses a change, Conductor says so on the screen and changes nothing; Threads keep working.
Each planning permission is given per role and checked in the Value Group, Team or Workspace where you work.
Conductor with AI switched off: what that means, and the three switches that must all be on before AI runs anywhere.
A new organisation starts with AI off. AI only runs where the organisation's, the Team's and the Module's switches are all on.
Connect file shares over SMB, SFTP, FTP(S), WebDAV and NFS, test a connection, set attachment limits and AI access per system.
Administrators connect Conductor to file shares and repositories under Administrator, Systems (permission settings.manage_connections).
Add a file share connection step by step: type, provider, name, address, limits and which Workspaces may use it.
Address: smb://server/share, optionally with a folder: smb://fs1.gemeente.example.nl/projecten.
Address: sftp://host[:port]/path, port 22 when not given.
Address: ftps://host/path for an encrypted connection (explicit TLS on port 21), ftp:// for an unencrypted one.
WebDAV (Nextcloud, SharePoint and others): an https:// address with username and password.
Largest file (MB, at most 100): default 25. All files of one thread together (MB): default 250, at most 10240.
Test connection in the list lists the share's top folder, writes a small file named .conductor-connection-probe, reads it back and deletes it.
Per connection, AI access is Off (the default), On within the path rules, or Suspended.
Removing a connection cannot be undone; Modules that used it can no longer store files.
Invite people, give roles, archive and restore accounts, export or erase someone's personal data (GDPR), and what each role may do.
Administrator, Users (permission users.view) lists everyone with their roles, status and whether they set up sign-in codes.
Invite a person by e-mail; they get a link to set their own password, valid for 72 hours. Re-invite sends a new link.
Click Edit Roles (permission users.assign_roles). Tick Organisation-wide roles, or give a role at one Workspace, Value Group, Team, Project or Module.
Remove (archive) (permission users.deactivate) archives a person. They can no longer sign in and every session ends.
Export data (organisation administrators only) downloads a JSON file with the person's record, every document that names them, their audit records, their erasure…
Erase a person's personal data after 30 days, cancellable until then. Their work stays, shown as Removed user.
Administrator, Roles (permission roles.view) lists the roles. They are your organisation's own: rename them, change what they grant, add or delete them.
Your organisation's sign-in address, the e-mail code at sign-in, identity providers over SAML and OIDC, and SCIM.
Administrator, IAM (permission settings.manage_scim) holds everything about signing in.
Require email code at sign-in makes every password sign-in ask for a 6-digit code by e-mail (see “The e-mail code (two-step sign-in)”).
Click Add identity provider. Only one provider is active at a time. In the provider list: Edit, Test, download the SP metadata (SAML), Activate, Enforce and Delete.
With SCIM your identity provider creates, updates and archives people in Conductor automatically.
The Administrator tabs, your licence, and the audit log.
What each Administrator tab is for, and the permission it needs: License, Users, Roles, IAM, Audit log, Privacy and more.
Your licence and seats, and the connections to Blueprint and Strategy.
The audit log shows who did what and when. Filter on From, To, Source and Event types, and download with Export CSV or Export JSON.
Erase archived users automatically: Never (keep archived users) (the default), or after 3, 6, 12, 18, 24, 36, 60 or 120 months.
Default language: English, Nederlands or Français, or Not set (each person's browser language).
Workspace, Settings has these tabs: Workspaces, Value Groups, Projects, Phases, Labels (the Workspace's own words), Products/Services, Templates, Iterations (the sprint…
Every limit in one table: links, passwords, codes, search, labels, exports, attachments, states and more.
Every limit in one table: links, passwords, codes, search, labels, exports, attachments, states and more.
Configure security, projects, issue types, and field mapping
Configure authentication, role-based access controls, and data protection for your Jira plugin.
Enable Taskstreamer for specific Jira projects and configure project associations.
Select which Jira issue types are plannable by the Taskstreamer scheduling engine.
Map custom fields, configure issue type handling, and set up project-specific sync rules.
Plan features directly from Jira issue pages
Plan features directly from Jira issue pages with multi-team assignments, sprint estimates, and dependency management.
Taskstreamer administration and customization
Organizational structure, team capacity, and role assignments
Configure terminology matching your organizations.
Define Roadmap settings and Themes per Project Products & Services for one or more Value Groups
Define the fields you want per Objective to detail the What and the How per Objective
Define your sprint cadence and if applicable, your Program Increments
Activate & configurare the Kanban board to track the Objective refinement
Organizational structure, team capacity, and role assignments
Organize teams into Value Groups (ARTs, Trains, Domains) with capacity settings and role assignments.
Strategic objectives and roadmap management
Visual quarterly timeline of strategic objectives organized by building blocks.
Refine objectives with detailed descriptions, acceptance criteria, and feature linkage.
Feature management, prioritization, and team assignments
Manage features in a prioritized grid with team assignments, dependencies, and automatic plan recalculation.
Timeline views and automatic scheduling
Gantt-style timeline showing scheduled work across teams with sprint-level granularity.
Program Increment planning and sprint configuration
Define Program Increment boundaries, sprint cadence, and planning horizons.
Track sprint-by-sprint progress within a Program Increment with burndown and velocity metrics.
Stay informed with multi-channel alerts for priorities, features, and deadlines
Multi-channel notification system with in-app alerts, email digests, and browser push for priority changes, feature updates, and deadline breaches.
Configure delivery channels, email digest frequency, browser push opt-in, and per-type overrides for each notification category.
Your strategic overview and portfolio health
Your strategic overview showing portfolio health, progress metrics, and quick navigation across all Value Groups.
Cross-portfolio organizational structure and alignment
Bird's eye view of your organization's structure, Value Groups, and cross-portfolio alignment.
Strategic planning frameworks and execution linking
Define strategic direction using OGSM or OKR frameworks with execution linking to Jira features.
Export strategies and roadmaps to presentation-ready PowerPoint slides.
Capture, evaluate, approve and track strategic ideas and business needs
Navigate the pipeline from idea to delivery — create, manage, and track epics through structured stages.
Score epics against strategic criteria, compare candidates, and make transparent approval decisions.
Break approved epics into concrete demand items and assign them to Value Groups for delivery.
Monitor demand absorption across Value Groups with dashboards, progress tracking, and capacity views.
View shared strategies and epics in Jira, and suggest delivery objective links for strategic alignment.
Cross-portfolio roadmap views and filtering
Combined roadmap view across all Value Groups with filtering by department, status, and time period.
What-if analysis and scenario planning
Simulate different priority scenarios and analyze their impact on timelines and resource allocation.
User management, roles, and system configuration
Manage users and their access to the Strategy Application.
Define and manage user roles and permissions across the platform.
Configure epic evaluation criteria, scoring weights, and approval roles for the Ideation & Demand pipeline.
View and export system audit logs for compliance and troubleshooting.
Configure connections between the Strategy Application and Jira instances.