Productboard logo Productboard automation · runs weekly

Update Productboard feature statuses after a release

The release goes out on Thursday, and the board still shows half of it as Delivery until someone clicks each status icon.

Cotlet does it in your own Productboard account with list_feature_statuses, search_features, get_feature and update_feature_status, called by your AI agent, an n8n workflow or a script.

Sign up free All Productboard tools

Hosted · nothing to install or maintain

Can Productboard do this on its own?

Productboard changes a feature status by hand, through a Jira rule, or through the Entities API (checked 22 Oct 2026). The Jira rule needs a connected issue and does not apply to past changes. The API needs a token from a workspace admin on the Pro plan or higher.

How you do it in Productboard today

  1. The PM opens a feature and clicks the colored status icon next to its name.
  2. A list of statuses opens, and the PM picks the new one. Features and subfeatures share the same list.
  3. The statuses themselves live under Settings > Item customization at the bottom of the Main menu, where Business and Enterprise plans can rename, reorder or add them.
  4. With a Jira integration, a rule can map a Jira issue status to a Productboard status, and the feature changes when the issue does.
  5. Features that shipped without a Jira issue, or from a plain release list, are changed one at a time by hand.

How to update Productboard feature statuses after a release

Prompt

Here is the list of features we shipped this week. Set each one to Launched in Productboard. Skip any that are not in Delivery or Testing and tell me why.
  1. 01

    Learn the workspace statuses

    list_feature_statuses runs first, because custom statuses are named by each workspace. The agent matches "Launched" in your prompt to the exact name in the list and stops if no status fits.

  2. 02

    Find each feature by name

    search_features looks for every line of your release list. A name with two matches is not changed; it comes back to you with both candidates.

  3. 03

    Check where it stands

    get_feature shows the current status. Your prompt says which statuses may move, here Delivery and Testing, so a feature still at Discovery or already Launched is skipped with that reason.

  4. 04

    Change the status

    update_feature_status runs once per feature and waits for your OK on each call by default. You can approve the whole batch from one reply.

  5. 05

    Report the changes

    The agent lists each feature with its old and new status, and the ones it left alone with the reason.

What you get back

Example data

Release list: 7 features
Set to Launched 5, e.g. CSV export (Delivery to Launched)
Skipped 2:
- Dark mode (still in Discovery)
- Saved filters (two features share the name)

Other ways to ask

  • Move everything in Testing that appears in this changelog to Launched.
  • Show me every feature in Delivery with its owner, and change nothing.
  • Set the features in this list to Planned for delivery and tell me which ones were already further along.

What Productboard allows, and what to know first

  • Productboard shows statuses as a colored icon next to the item name on features, subfeatures, objectives, initiatives, key results and releases.
  • Productboard features and subfeatures share one status list, and custom statuses need the Business or Enterprise plan.
  • Productboard asks you to reassign items when you delete a status that is still in use.
  • On the Enterprise plan, a lifecycle rule under Settings > Lifecycle rules can require fields before a feature moves to a status.
  • Productboard keeps statuses apart from tasks and health updates: completing a task does not advance a feature, and health uses On track, At risk and Off track.

update_feature_status asks for your OK by default. To run it weekly without you, switch confirmation off for that tool in your dashboard.

Sources: Productboard Help: Customize status values for items · Productboard Help: Control your product lifecycle with required fields · Productboard Help: Update a feature status from a Jira issue status · Productboard Help: Provide health updates for your features

Call update_feature_status from a script

curl

curl -X PATCH https://cotlet.dev/api/v1/productboard/features/ft_4d7e10/status \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"status":"Launched"}'

Example response

{
  "feature_id": "ft_4d7e10",
  "name": "CSV export",
  "status": {
    "previous": "Delivery",
    "current": "Launched"
  }
}

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is productboard_write → update_feature_status. Example data.

Schedule it in n8n, Make, Zapier or cron

Productboard tools this automation uses

Cotlet Productboard tools used to update Productboard feature statuses after a release
Tool Parameters
list_feature_statuses none
search_features query, status, cursor
get_feature feature_id
update_feature_status feature_id, status
All 12 Productboard tools with descriptions

Frequently asked questions

Is it safe to connect Productboard to Cotlet?

Yes. You sign in to Productboard yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get Productboard once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

Give your agent access to Productboard.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with Productboard.

Sign up free