Enhancer for Plane — Chrome extension: issue templates, open work items by key, copy reference, focus mode #9406
gaerae
started this conversation in
Show and tell
Replies: 1 comment
|
Update — quite a lot has shipped since this post, so I've rewritten the description
If you tried an earlier version and something felt missing, I'd genuinely like to |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I run Plane for my team and built an unofficial Chrome extension to fix the everyday
frictions we kept hitting. It started with templates; it has grown into a small toolbox.
Works on Plane Cloud and self-hosted, entirely client-side — nothing installed or
changed on the Plane server.
What it does now:
issue PROJ-123in the address bar to jump to a work item.Also via right-click on a key selected in any text (Slack, PR titles). Targets are
just URLs with
{{key}}, so you can register Jira / Linear / GitHub / GitLab tooand route by key prefix — handy mid-migration.
Alt+Shift+Fhides the side panels, per tab.rule. A visual element picker builds the selector for you, no DevTools.
Alt+C) copies the item as plain text, a Markdownlink, or a branch name. Formats are editable with
{{item.key}},{{item.title}},{{item.url}}.create-work-item modal fills the title + a Markdown body in one click (
Alt+T).Variables like
{{date}},{{date+7}},{{week}}and up to 5 of your own(
{{var.name}}) are filled on insert.(intranet, Git raw, S3) and everyone pulls the same templates on a schedule.
Synced templates are read-only, so the source stays the single place to edit.
Privacy by default: ships inert — no active domains, no host permissions until you
enable it on your Plane site, no accounts, no tracking, no remote code. MIT-licensed.
Two questions for anyone who tries it:
pack and would like to make it more realistic.
All reactions