Plan requirement
| Subscription | Suite Professional or higher, Explore Professional or higher |
| Access | Agent |
Cloning is how most reports should start, and it is the habit that keeps the standard ones intact.
Clone one
- Open the report closest to what you want.
- Clone it.
- Rename it immediately.
- Change what needs changing.
- Save.
Rename before you edit
"Copy of tickets solved" lives for years otherwise, and after three of them nobody can tell which is the one in use. Rename first, while you still know what you intended.
Why clone rather than build
A standard report already has the right dataset, sensible filters and a working visualisation. Changing one thing about something that works is faster and less error-prone than assembling it.
It is also how you learn the builder, by seeing how a good report is constructed.
Never edit a standard report
They are the reference point, and they are used by the standard dashboards. Editing one changes every dashboard showing it, including ones other teams rely on.
A clone does not follow the original
Fixing the original later does not fix your copy. Where several clones exist of the same thing, a correction has to be made in each, and one will be missed.
That is the argument for keeping the number of clones small.
Check the filters you inherited
Clones carry the original's filters, including a date range or a brand exclusion that made sense there and not here. Read them before trusting the number.
Delete the experiments
Cloning is cheap, so the report list grows. Half an hour once a quarter removing what nobody uses keeps it navigable.
Comments
0 comments
Article is closed for comments.