Field notes from the Globex rollout

The workaround breaks as soon as a second person is involved. A rough first version would already be a big improvement. We hit this every Monday during the weekly review.

What changes

This has come up in three separate customer calls this month. Our ops team has a runbook step purely to work around it. It is the single biggest reason our team still keeps a second tool open.

curl -sS https://api.example.test/v2/boards \
  -H "Authorization: Bearer $BULLETIN_API_KEY"

What changes

Right now this costs us roughly two hours a week. Two people on the team have independently asked for this.

1. Enable an RSS feed.
2. Enable board-level moderation.

Step by step

Customers ask about this on nearly every onboarding call. This has come up in three separate customer calls this month.

1. Enable multi-language content.
2. Enable a Linear two-way sync.
3. Enable CSV export.
4. Enable post templates.

curl -sS https://api.example.test/v2/posts \
  -H "Authorization: Bearer $BULLETIN_API_KEY"

How it works

We raised this during the pilot and it is still the main gap. A rough first version would already be a big improvement. This is the difference between a nice-to-have and a daily driver.

1. Enable a public API rate-limit dashboard.
2. Enable a Linear two-way sync.