Design: Copy a dashboard to another organisation

[RomijnHumanoids]

There is already a design for copying an organisation dashboard to the 'all organisations' view of an install.

Now, this will need a similar flow for adding the settings of a dashboard to another organisation in your install. This has some implications as not all reports/tags are the same between the two organisations, so object list filters or report sections might not work on other organisations.

[underdarknl]

For the object and finding dashboards we could very easily implement a copy function as they are based on queries.
For report-dashboards, we could do the same, but we'd need to copy the recipe and schedule, and the recipe should be based around a query.

[RomijnHumanoids]

Design for review, Figma link.

Considerations in this design about copying dashboard (items) to other organisations:

• Copying a Object/Findings list item;
  With unhappy flow when filtered on elements like ‘tags’ are not recognised in the receiving organisation.
• NOT copying a report section items;
  As reports that are not saved in the receiving organisation.
  Possibly copying the whole report recipe to the receiving organisation, but the query or separately selected objects will not match the receiving organisation.
• NOT copying a complete dashboards; this might have multiple items with different errors;
  1. report sections of reports that are not saved in the receiving organisation,
  2. lists filtered on elements like ‘tags’ that are that are not recognised in the receiving organisation.

Open questions to be decided on:

• When tags are used in the lists applied filters, we have to decide whether to copy/create the tags in the receiving organisation, or to extract the tags from the filters. I think the latter makes more sense, because otherwise the list will be empty until the tags are to be subjected to objects in the receiving organisation. But I haven't checked this with stakeholders.