Guides· 9 min read

Feature Announcement Video: Make One From a Linear Ticket

Use the PR merge as the trigger, five lines from the ticket as the brief, and Linear's customer requests as your first audience, then ship a 60-second clip the same day.

By disha Sharma

ShareXLinkedIn
Feature announcement video guide cover: a ticket-to-video card showing a Fixes ENG-123 to Done trigger, four timed script beats and where to send the finished clip

A user-facing Linear ticket already holds most of a feature announcement video: the problem, what changed, who it's for and how to try it. What's usually missing is a trigger. The video gets made "when marketing has time", which means a week after the feature ships, or never.

The short answer: treat the Linear ticket as the brief and the PR merge as the trigger. When a PR with Fixes ENG-123 merges, Linear moves the issue to Done on its own. That's your cue. Pull five lines from the ticket, write a script of about 150 words (roughly 60 seconds at a normal speaking pace), and record the feature on the merged build. Then send the video to the people who asked for the feature. If your team uses Linear's Customer Requests, that list is already on the ticket.

Two things make this work better than a generic "how to make a launch video" process:

  • The trigger is automatic. You don't need a reminder or a weekly marketing sync. The Done status tells you a feature is live.
  • The audience is named. A ticket with customer requests tells you exactly who to send the video to first, before any public post.

Below: which tickets deserve a video, what to pull from the ticket, a 60-second script template, how to build the video, and where to send it on merge day.

Which Linear Tickets Deserve a Video

Most tickets don't. A changelog full of videos for dependency bumps trains people to ignore all of them.

Make a video when at least two of these are true:

  • The change is visible. A user can see it or click it in the product.
  • Someone asked for it. The ticket has customer requests, or support has heard the question more than once.
  • It changes a workflow. It removes steps, unlocks something new, or moves a button people rely on.
  • Sales or support will be asked about it this week.

Skip the video for refactors, small copy fixes, internal admin tools and anything still behind a feature flag for the people you'd send it to.

The rule: if you can't name who will watch it, don't make it.

Make the PR Merge Your Trigger

Linear's GitHub integration links a pull request to an issue when the issue ID appears in the branch name, the PR title or the PR description (Linear docs). Copy the branch name straight from the issue with Cmd/Ctrl + Shift + ..

By default, a linked issue moves to In Progress when the PR opens and to Done when it merges. Use a closing magic word such as Fixes ENG-123 or Closes ENG-123 in the PR. Linear's docs explain that non-closing words like Part of ENG-123 move the issue through other statuses but don't apply the merge status. So a feature split across several PRs only hits Done when the final one, the one with the closing word, merges.

That gives you a clean trigger:

  1. Agree that any user-facing issue with a needs-video label gets a clip.
  2. Make a saved view in Linear: label needs-video, status Done, completed in the last 7 days.
  3. Whoever owns release notes checks that view on release day.

Teams can also change which events move an issue, such as "ready for merge", in the team's workflow automations. If your team ships behind flags, the merge isn't the release, so check the flag before recording.

The takeaway: let Linear tell you when a video is due instead of relying on someone's memory.

What to Pull From the Ticket

Don't paste the whole thread into a script. Comment threads are full of debate, dead ends and internal names. Pull five lines:

From the ticketBecomes in the videoExample
TitleWorking headline, rewritten in user words"Bulk-assign seats from CSV"
Problem or contextThe opening line"Adding 40 teammates meant 40 invite forms."
What shippedThe main claim"Upload a CSV and assign every seat at once."
How to try itThe on-screen path and the closeSettings > Members > Import
Audience labelWho the video is for, and who gets it firstAdmins on the Team plan

If a field is empty, fix the ticket before writing the script. A video can't explain a feature the ticket never described.

Two fields matter more than they look. The feature name should match what appears in the UI exactly, not the internal ticket name. And the how to try it path should be checked on the production build, not copied from the ticket written weeks earlier.

If you use an AI assistant to draft the script, Linear runs an official MCP server that lets assistants such as Claude, Cursor and VS Code read issues and comments (Linear docs). Use the read-only endpoint, https://mcp.linear.app/mcp/readonly, so the assistant can read the ticket but can't change it.

The rule: five lines in, one script out. Everything else stays in Linear.

A 60-Second Script Template

At about 150 spoken words per minute, the average rate measured by the National Center for Voice and Speech, a 60-second video holds roughly 150 words. Short is right here: Wistia's data shows videos under one minute average a 52% engagement rate (Wistia), and a feature announcement only needs to say what changed and where to find it.

BeatTimeWordsWhat to say
Problem0:00-0:08~20The pain, in the user's words
What shipped0:08-0:18~25Feature name and the one thing it does
Show it0:18-0:45~65The click path, start to finish, on screen
Who gets it0:45-0:52~20Plan, role, and "available now" or "rolling out"
Try it0:52-1:00~20Exact menu path or link

Here's the template filled in for the example above. It runs 117 words, a little under 50 seconds read aloud:

Adding a new team used to mean filling in one invite form per person. For forty people, that's forty forms.

Now you can bulk-assign seats from a CSV.

Go to Settings, then Members, and click Import. Upload a CSV with one email per row. You'll see a preview of every row first: new invites, people who already have a seat, and any emails that don't look right. Fix those, choose a role for everyone, and click Assign. Each person gets an invite email straight away.

Bulk import is available now for admins on the Team and Business plans.

To try it, open Settings, then Members, then Import. Our help center has a sample CSV you can download.

The example is made up to show the structure. Use your own feature, plan names and menu path.

The takeaway: open with the problem, not the ticket ID, and end with where to click.

How to Build the Video

Record the real feature. Record the click path on the merged build, using a demo account with fake data. A screen recording proves the feature works exactly as shown, which matters more for an announcement than polish. On a Mac, our guide to screen recording on Mac with audio covers the built-in options.

Or start from the code. If the feature lives in a repo you can share, Poko Motion can start a video from the repository itself. It pulls real components, copy and styling from the code to build accurate UI scenes. A screen recording works too: Poko uses it as real footage and builds motion and narration around it.

Don't give Poko the ticket as a PDF. Poko treats a PDF as a research paper and switches to its slower, voiceover-led explainer style, which is wrong for a 60-second announcement. Our guide to which source to give Poko explains the difference. Paste the five lines into your prompt instead.

Then edit by typing. Useful prompts:

  • "Open with the problem, not the feature name."
  • "Cut to 60 seconds."
  • "Use the exact button labels from the UI."
  • "End on the menu path: Settings > Members > Import."

Add captions and check every frame. Many people watch with the sound off, and captions for prerecorded video are a baseline requirement under WCAG 2.1. Pause on each frame and check for real customer names, internal tool names and unreleased features in the sidebar.

The rule: show the feature people can use today, on the screen they will actually see.

Where to Send It on Merge Day

Same-day beats perfect. Send the video in this order:

  1. The people who asked. In Linear, Customer Requests attach a customer to the issue, and the request shows on both the issue and the customer's page (Linear docs). You can export an issue's requests as CSV from the Cmd/Ctrl + K menu. Linear doesn't email those customers for you. Hand the list to whoever owns the account, or use your support tool's Linear integration.
  2. Sales and support. Post it in the channel where they'll be asked about the feature, with the menu path written out.
  3. Your changelog or release notes. Embed the video above the written entry. If you don't have a video changelog yet, here's how to build one.
  4. In-app or email. Only for features most users will notice.
  5. Social. Only if the feature is visual and public. Export a 9:16 version for vertical feeds.

Finally, paste the video link into the Linear issue as a comment. The next person who finds the ticket gets the explanation with it, and you'll know which features already have a video.

The takeaway: the customer who asked for a feature is the best first viewer you have.

Your Next Step

Add a needs-video label in Linear and create the saved view: label needs-video, status Done, completed in the last 7 days. Pick one ticket from this week's view, pull its five lines, read the 150-word script aloud with a timer, and record it. Send it to the customers on the ticket before you post it anywhere else.

Disha Sharma
About the author

Disha Sharma

Marketing, Poko Motion

Writes about AI video workflows, product storytelling, and motion video.

Questions, answered.

How do you make a feature announcement video from a Linear ticket?

Wait for the PR with a closing magic word such as Fixes ENG-123 to merge, which moves the issue to Done. Pull five lines from the ticket: title, problem, what shipped, how to try it and audience. Write a script of about 150 words, record the click path on the merged build, add captions, then send the video to the customers on the ticket before posting it publicly.

How long should a feature announcement video be?

Aim for 45 to 60 seconds. At the average speaking rate of about 150 words per minute, measured by the National Center for Voice and Speech, that's 110 to 150 words. That's enough for the problem, the feature name, the click path, who gets it and where to find it. Wistia's data shows videos under one minute average a 52% engagement rate, so link to docs instead of stretching the video.

What should a feature announcement video script include?

Use five beats. Open with the problem in the user's own words. Name the feature exactly as it appears in the product. Show the click path on screen from start to finish. Say who gets it, by plan or role, and whether it's available now or rolling out. Close with the exact menu path or link. Leave out ticket IDs, internal names and the story of how the feature was built.

When does Linear mark an issue as Done automatically?

With Linear's GitHub integration, a linked issue moves to In Progress when a PR opens and to Done when it merges, by default. The PR needs a closing magic word, such as Fixes ENG-123 or Closes ENG-123, in its title or description. Non-closing words like Part of ENG-123 move the issue through other statuses without applying the merge status. Teams can change these rules in their workflow automations.

Who should see a feature announcement video first?

The customers who asked for the feature. If your team uses Linear's Customer Requests, each request appears on the issue and on the customer's page, and you can export an issue's requests as a CSV. Linear doesn't email those customers for you, so give the list to the account owner or use your support tool's Linear integration. Then share it with sales and support, and add it to the changelog.

Keep reading

#feature announcement#Linear#product launches#changelog#product management#video scripts#product videos

Poko Motion · the fastest AI motion video generator

Make your first video
in 5 minutes.

Paste a link, a doc or a deck. A swarm of AI agents builds the video while you watch.