makeplane / makeplane/plane

[feature]: Allow video attachments in ticket comments

Open
#7,867 2 comments 9 reactions 2 assignees View on GitHub

@vihar is already working on this.

Since Sep 29, 2025.

✨feature plane
Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Is there an existing issue for this?
  • I have searched the existing issues
Summary

Currently, Plane does not support attaching videos directly in ticket comments.
In QA workflows, especially when failing a ticket, it is critical to attach short screen recordings to demonstrate bugs clearly.

Right now, the workaround is to upload videos to Google Drive/Dropbox and paste links in comments.
However, this is inefficient and makes tickets harder to track.

Feature Request:

  • Support direct upload of video files (e.g., .mp4, .mov, .webm) in comments.

    Benefits:

  • QA → Developer communication becomes faster.

  • No reliance on external links.

  • Easier debugging and ticket tracking.

Why should this be worked on?

Video attachments are critical for QA, product, and developer collaboration.
When reporting bugs, a short screen recording often communicates the issue far better than text or screenshots.

Without direct video uploads in comments:
• QA engineers must upload videos to external platforms (Google Drive, Dropbox, etc.).
• Developers then need to open external links, which is time-consuming and sometimes restricted by permissions.
• Over time, external links may expire, leaving tickets incomplete.

Adding direct video support will:
• Improve clarity of bug reports.
• Save time for QA and developers.
• Ensure long-term accessibility of test evidence inside Plane.
• Make Plane a more complete end-to-end issue tracking system.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.