Assign a Workspace Project to multiple Report Suites

[#1]

The issue is that In Workspace a Project is made for ONE report suites. So when the Project is selected it will show data for that specific Report Suite.

We planned to make generic Project, like Traffic Source, Browsers, Payment etc, that can be used across all or many reports suites.

So our plan was to make these project and then select Report Suites it was relevant for. But we realized that is not how Workspace works.

Instead is required that we copy the project and save one for each Report Suite.
And include a reference for the report suite in the naming, because there are not a "Report Suites" column in the overview !.

The solution would be to have a option to assign multiple report suites to one project. It should not be a copy, but a relationship.
And it is only Admin's that can save changes to the Project, because that will be reflected for all Report Suites.

In that way we would be able make generic Project that can provide the basic reporting need for most Report Suites/Virtual Report Suites.

Below i have tried to visualize how it could look. When you create and manage a Project, i can select what report suites to assign it to. If more than one is selected it will show as "multiple".

If this is combined with one of my other ideas - Select Report Suite from Workspace startpage

We would on the Workspace start page limit the number of identical Project, made for different Report Suites.

[#2]

Great news!  We just recently released the ability to create custom Workspace templates, which work very similarly to how you've suggested.  You can create a project and save it as a template.  Then, when anyone loads this template, it will not use the template it was saved with, but whichever report suite they are using (they can also change the report suite at any time).  Now you shouldn't have to make a bunch of copies.

[#3]

Unless i have misunderstood Templates, they don't act as a "Base reporting" for "admin-selected" (virtuel) Report Suites.

They are what they say - Templates -  a user can choose to use - which is great.

I can also choose to save one for each report suites, if i want to avoid that all the "normal users" do it.

So as i see it, it doesn't solve the issue we will have when all users, have to build there own portfolio of "Projects".

This idea need to be seen in combination with the idea - Select Report Suite from Workspace startpage

Those two combined, would for me make a strong setup, for the regular user whiteout the high exploration needs.

[#4]

I apologize, but I'm not understanding why templates don't fulfill what you're trying to do.  I can understand that you would want to choose a report suite first (your other idea that you mentioned), but you could create one template that would work for any number of report suites - you just need to pick the report suite once you load the project and it should work.  But I'm sure I'm missing something from your description.

[#5]

Templates are a great feature. And it will help us in many cases.

But it is not my own (admin user) need/understanding i'm worried about.

It's the more average user.

The essence of the issue is in your sentence: "...you just need to pick the report suite once you load the project and it should work". 

For many of our users this will be a new way of working with the data. They normally don't "create" and save any "reports" them self. They are consumers of reports.

But let's see if we can get them working in a new way.

[#6]

Got it, thanks for your added clarification.  We would appreciate your continued feedback as you work with the report consumers, because we may need to change things in order to accommodate their needs (as you're suggesting).  We'll also consider the "select report suite first" idea.  Thanks.

[#7]

Marking as a duplicate of Multiple Report Suites in one Workspace project - show your support there!