Roadmap and releases

The Roadmap and Releases tabs sit next to Inbox on the Feedback & roadmap page. The roadmap is the list of features to build, ranked by priority. Releases list every update to roofingBoss, newest first. Open Sidebar → Settings → Feedback, then click Roadmap or Releases.

Only admins can use these tabs. The roadmap and releases are saved in roofingBoss only. JobNimbus never sees them.

How the roadmap updates itselfCopy Anchor Link

You don't have to keep the roadmap current by hand. When a developer has turned on release tracking, three things happen:

• Each time an update ships, it's added to Releases with a short summary. The developer writes the summary along with the change. When they didn't, Claude reads the change and writes it. When the update delivers a roadmap item, that item moves to Shipped. Follow-up work the change leaves for later goes into Backlog as a Developer idea or a Claude idea. If people should check something by hand, a QA check card lands in the Inbox. See Run QA checks.
• Every Monday, Claude reviews the roadmap and the team's feature requests. It suggests an impact and effort for items that aren't sized and links requests to the items they ask for. It also adds ideas for requests no item covers and picks what to build next. See Read Claude's picks.
• Claude never sizes an item on its own. Its sizing is a suggestion until an admin clicks Use this sizing.
• Claude needs an API key, which an admin saves in Settings → Integrations → Claude. Without a key, the Monday review doesn't run, and an update that arrives without notes is recorded from its description only.

Read Claude's picksCopy Anchor Link

Claude's picks for what to build next sits at the top of Roadmap. It shows when Claude last reviewed the roadmap, a short summary, and up to three items to build next, each with the reason. Click a pick to open the item.

Work the boardCopy Anchor Link

Switch between Board and Priority with the tabs.

The board has four columns: Backlog, Next up, Building, and Shipped, each with its count. Within a column, the highest priority comes first. Shipped shows the newest items first and keeps the latest twelve. To see them all, click Priority and pick Shipped.

A card shows:

• Its priority, such as Priority 18, or Needs sizing until it has an impact and an effort.
• Developer idea or Claude idea when an update or Claude's review added it, or From a request when someone made it from a feature request.
• The title and area.
• Claude suggests… with the impact and effort Claude suggested, when that's waiting on you.
• How many requests are linked to it, and its sizing (or the day it shipped).

To move an item to another stage, drag its card to another column. The change saves right away. If it can't be saved, the card goes back and you see Couldn't move that card, so it went back. With the keyboard, use Space to pick a card up and put it down, the arrow keys to move it, and Enter to open it.

Rank by priorityCopy Anchor Link

Click Priority to see items in a table, highest priority first: #, Item, Impact, Effort, Requests, Priority, and Stage. It starts on Still to build (Backlog, Next up, and Building). Pick a stage to see only that one, including Won't do.

Priority is impact divided by effort, times ten. Each linked request raises it by a fifth, up to five requests (double):

Add an itemCopy Anchor Link

1. Click New item.
2. Write a Title and, if you like, a Description and an Area such as Work orders.
3. Pick a Stage, and an Impact and Effort if you know them.
4. Click Add to roadmap.

To make an item from a feature request, open the request in Inbox and click Add to roadmap. See Link a report to the roadmap.

Open an itemCopy Anchor Link

Click a card or a table row. You can change the Title, Description, Area, Stage, Impact, and Effort, then click Save.

• Claude suggests…: click Use this sizing to take Claude's impact and effort, or Dismiss to drop the suggestion.
• Requests: the reports linked to the item, with who sent each one. Click a name to email them, for example to say the feature shipped. Linked by Claude marks the ones the weekly review linked. Click the × on a request to unlink it.
• Added: who added the item, and for an idea that came with an update, that update.
• Shipped: when it shipped, and the update that shipped it.

To delete an item, click Delete, then Delete to confirm. Its requests stay in the Inbox. To keep a record that you decided against something, move it to Won't do instead.

Check what shippedCopy Anchor Link

Releases lists every update to roofingBoss, newest first. Each one shows the date, its number (such as #276, which opens the change on GitHub), the area it touched, its title, and a summary. Below that you may see:

• Shipped from the roadmap: items this update delivered.
• QA checks for people to run: checks the update added to the Inbox, with their status. Click one to open it.
• Follow-ups added to the backlog: ideas the update added for later.

Behind the scenes marks updates people won't notice, such as speed or reliability work. Turn on Only changes people will notice to hide them. Written in the PR along with the change. means the developer wrote the summary, checks, and follow-ups when they made the change. From the PR description. Claude didn't review this one. means the summary was copied from the developer's notes, with no checks or follow-ups.

Run QA checksCopy Anchor Link

A QA check is a card an update adds to the Inbox when a person should try something in the app before everyone relies on it, like totals that must match JobNimbus or a schedule change. QA checks have the type QA check, start in New, and come from Developer or Claude with the update's number, such as Developer (#276).

1. In Inbox, set Type to QA check.
2. Open a card. It lists the steps and why a person should look. Page opens the page to check, and Release opens the update.
3. Follow the steps. Write what you found in Internal notes or a comment.
4. Move the card to Resolved when it checks out, or leave it In review and tell the developer what's wrong.