getsentry / getsentry/sentry

Improve dashboard template copying

Open
#86,776 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

Problem: Currently, when you want to use a template, you click "add dashboard" and then we just create a dashboard with the exact same name (e.g. Backend template), in viewing mode. If the name is taken, we do append "copy", then "copy 1" but not the first time. This can result in some confusion, e.g. this anecdote:

> huh, I looked at this again and I’m not sure how I screwed this up. I think the old name of the dashboard may have had “Template” in it. perhaps the feature request is that when you do “Add Dashboard” from the list across the top, you are asked to give it a name. It’s confusing that e.g. the Mobile Template Add Dashboard button adds a dashboard called “Mobile Template.”
what we do today is pre populate the name wiith “template” which may sometimes add confusion. the customer here is suggesting we make the name field manadotory and not autopopulate it
:+1:
rationale:
yeah, so what I think happened was a long time ago nova cloned “Systems Template” and if there’ no extant dashboard with that name, the new dashboard will also be called “Systems Template.” so I saw the dashboard named “Systems Template” and edited it, thinking it was a template, not an instance

Suggested solution:
- append "copy" from the first time the template is used
- open the dashboard in "edit mode" in order to encourage the user to rename their dashboard.

Contributor guide

Open the contributing guide

Research direction

Start from the dashboard list's “Add Dashboard” flow and trace how a template is copied and opened. Verify that the first copy is named with “copy” and that the new dashboard opens in edit mode; done means both behaviors work consistently without the original template name causing confusion.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.