BOILERRUM / Tasks
Turn a shared ideainto a clear next step.
Make work visible with owners, priorities and a workflow. Move between a board, backlog and roadmap without losing the idea that started the work.
Captured in Boilerrum with an illustrative project. The app interface is shown in English.
Team planning · Kanban · Sprints · Roadmaps
The right level of detail
Break work into epics, stories, tasks, subtasks and bugs. Add priorities, estimates, start dates and target dates so each item has a clear place in the plan.
A view for the work in front of you
Use Kanban for status, a backlog for what comes next, sprints for a focused period and a roadmap for the longer view. Define statuses and permitted transitions around your process.
Make dependencies explicit
Connect related work with blocks, depends-on and duplicate relationships. Use milestones to mark meaningful outcomes, and keep task references close to the source document or canvas.
Inside the workspace
Explore the details
Build a hierarchy that respects the work
Break an outcome into supported levels: Epics contain Stories, Tasks or Bugs; Stories contain Tasks or Bugs; Tasks contain Sub-tasks. The Parent issue selector offers compatible records from the current project and excludes cycles. Keep the broader Epic association alongside the direct parent, then add an assignee, priority, estimate and components in Details. Inspect the same hierarchy in Roadmap, where unscheduled rows remain visible until you deliberately give them dates.
Issue details → Type / Parent issue / Epic; Roadmap → Add child issueMake each status move meaningful
Add a board column with a title and category to create a corresponding workflow status. Open Manage workflow to inspect the graph and connect the status transitions your process needs. Card moves across columns and Status changes in Details use the same transition rules, so a rejected move remains visible as a problem to resolve. Check a sample issue through the intended path and verify its final status before using that workflow for sprint completion.
Boards → Add column / Manage workflowPrepare the next commitment in one queue
Capture titled issues directly in Backlog, open their shared Details editor to refine the expected result, and drag rows to set the upcoming order. Move ready work into an open sprint section or use its Sprint field for the same planning decision. Sprint membership and workflow status remain separate, so placing an issue in a sprint does not claim progress. Clear temporary search and type filters before reviewing the complete priority order.
Backlog → ordered rows / sprint sectionsClose a sprint with a deliberate next destination
Create a planned sprint, add ready issues and start it with a name, goal and dates. Only one sprint can be active, and the dates are validated before the start succeeds. At completion, inspect the completed and unfinished counts. Done or terminal-status issues stay in the sprint history; unfinished work moves to Backlog or another non-completed sprint you choose. Verify the destination and each issue’s Sprint field after closing.
Backlog → Start sprint / Complete sprintDraw the sequence between scheduled outcomes
Drag a dependency dot from one scheduled roadmap bar onto another. Starting from the right creates a finish-to-start connection; starting from the left creates a start-to-finish connection to the opposite target side. Inspect the line alongside both date ranges and update dates as a separate planning action when needed. Connectors are saved with the selected roadmap. Click a line to inspect its named endpoints and remove an obsolete relationship through Delete Dependency.
Roadmap → scheduled bar endpointsPlan the same work across time
Inspect the issue hierarchy beside a timeline without recreating daily work in a separate list. Unscheduled rows stay in the tree and offer Drag to schedule when you are ready to set a real range. Move and resize bars to adjust dates, switch from Day through Half Year for the right horizon, and use Today to return to the present. Column Settings reveals status, assignee, due date and progress for the discussion at hand.
Roadmap → timeline / row hierarchyKeep the action and its context in one editor
Open the same live issue from a board, backlog or roadmap. Save a clear title with Enter and an expected result in Description with ⌘/Ctrl + Enter. Keep ownership, priority, estimate, parent and sprint beside the description, then use Comments for decisions and handovers. Reopen the editor to verify values and local-saving feedback. Deletion names its effect on comments and work logs while preserving and detaching child issues.
Issue card → Details → ActivitiesRecord effort with a useful explanation
Open Time Tracking from issue Details to log Time spent, update Time remaining or do both. Use duration notation such as 2h 30m. Time spent must be greater than zero and requires a Worklog description, while remaining-time updates can be entered separately. Save the form and inspect the Worklog tab to check the entry alongside the time summary. These activity records follow the same project-local saving boundary as the issue.
Issue details → Time Tracking → WorklogFind the right issue without losing the full view
Search board and backlog issues by key, title, description, assignee or reporter, then combine the query with one of the five issue types. Multiple search terms all need to match somewhere in those fields, ignoring case. Watch the visible-versus-total count to understand what is hidden. Open a result to verify its identity before editing, and use Clear issue filters to restore both the text query and type selection after the review.
Boards / Backlog → Search issues / All typesGive a delivery discussion useful checkpoints
Create named, colored layers for areas such as Design or API and assign relevant outcomes to them. The layer selector narrows the roadmap while retaining related hierarchy for context. Add a milestone with a title, due date and color, optionally associating it with a layer. Inspect its marker on the timeline, edit it as the plan changes and keep milestone dates distinct from the date ranges of the work that leads to them.
Roadmap → Manage Layers / Manage MilestonesTake a piece of work from capture to completion
BOILERRUM
Your team’screative reactor.
Bring the people, the thinking and the work into the same space.