Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Ability to Clone Dashboards #3103

Merged
merged 9 commits into from
Mar 31, 2018
Merged

Add Ability to Clone Dashboards #3103

merged 9 commits into from
Mar 31, 2018

Conversation

alexpaxton
Copy link
Contributor

@alexpaxton alexpaxton commented Mar 30, 2018

  • CHANGELOG.md updated with a link to the PR (not the Issue)
  • Rebased/mergable
  • Tests pass
  • Sign CLA (if not already signed)

Closes #3102

The Problem

  • Creating dashboards from scratch every time is time consuming and frustrating

The Solution

  • User can "Clone" dashboards from the dashboards index view

Preview

clone-dashboard

@ebb-tide ebb-tide assigned ebb-tide and unassigned ebb-tide Mar 30, 2018
@ebb-tide ebb-tide self-requested a review March 30, 2018 23:35
Copy link
Contributor

@ebb-tide ebb-tide left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LOOKS AMMAAAZINNG.

@@ -3,6 +3,7 @@
### Features

1. [#2526](https://github.com/influxdata/chronograf/pull/2526): Add support for RS256/JWKS verification, support for id_token parsing (as in ADFS)
1. [#3103](https://github.com/influxdata/chronograf/pull/3103): Add ability to clone dashboards
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so. this isn't quite in the purview of a code review: but noticed that maybe subsequent clones could be numbered instead of adding clone ad infinitum? might be a pain to implement though.
screen shot 2018-03-30 at 16 34 58

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That is the expected behavior. I wasn't sure off the top of my head the best way to handle this, as you'd have to look at all the existing dashboard names then decide whether to add a number or not

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I'm going to handle this in a separate PR

@alexpaxton alexpaxton merged commit a6671c3 into master Mar 31, 2018
@alexpaxton alexpaxton deleted the feature/clone-dashboards branch March 31, 2018 00:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants