Broccoli Docs

Appearance

Roadmaps ​

A Gantt-style timeline: fiscal quarters across the top, categories down the left, items placed across months.

Each item carries a status (planned / in-progress / completed / at-risk), a priority (P0–P3), story points, an owner, and — importantly — a ticket link.

Planning vs. Published ​

Roadmaps have a mode toggle that persists, so a manager can restructure a quarter without directors watching it happen live. Work in Planning mode, then publish when it's ready to share. Undo and redo cover five steps.

This is the step that turns a roadmap from a static picture into a live one. Put a JIRA key on a roadmap item and:

  • Status flows in from JIRA automatically.
  • Story points, acceptance criteria and assignee become visible.
  • The item appears in Team Health coverage metrics.
  • Pull requests that mention the key are matched to it.

You can also go the other way: open JIRA Live, select issues from the current sprint, and push them onto the roadmap directly.

JIRA data is cached for 30 minutes. If JIRA is unreachable, Broccoli shows the last good data rather than an empty board — check the timestamp before trusting a number in a review.

Sharing ​

A roadmap can be shared with a specific account as view or edit, independent of the broader role grants:

  • An editor cannot re-share a roadmap they were granted — only the true owner manages shares.
  • An editor cannot move a roadmap into their own team; ownership is preserved on every save.
  • View is not silent — someone with view access can still comment.
  • Sharing with a Director or Executive is automatically downgraded to view, even if edit is selected.
  • Team Access accounts cannot receive individual roadmap shares — they already see their team's roadmap through their role.

Team Health ​

A companion view that scores a roadmap against JIRA on planning hygiene: items with a ticket, story points, acceptance criteria, an epic parent, and an assignee. A low score usually means the plan is under-specified, not that the team is slow — check this before a leadership review.