Hi Rob

I am checking against the example project (Squawk workshop) - and I can create a new dashboard as a JazzUser (my permission from the webui ->Manage Users), and have a developer license. I am also part of the project area and team area

anthony

Have you assigned yourself a developer CAL? Only developers have the ability to create dashboards.

Note: The create dashboard button is only for creating private dashboards. If you click on your project in the left panel, you should see a default project dashboard created from a template. Once you have a developer CAL, you should be able to edit it freely!

Rob Retchless
Jazz Dashboards team

Hi Rob

I am checking against the example project (Squawk workshop) - and I can create a new dashboard as a JazzUser (my permission from the webui ->Manage Users), and have a developer license. I am also part of the project area and team area

anthony

Thanks Anthony. Unfortunately I wasn't using the Squawk example project (which I will get now and use as a baseline). I have a self-created project based on the 'Simple Team Process' and this only had the default roles and permissions. I have now created a 'project-lead' and 'team-lead' role on the project and given each role the necessary permissions to save and modify the dashboard at the project and team level. This now seems to have allowed me to do as I expected.

The odd thing which hadn't occurred to me is that for an individual user to be able to create and manage their own personal dashboard, it would seem that they must be allocated the ability to manage their own dashboard within the project properties. I would logically have expected this to occur at the user administration level. Unless I have missed something else obvious.

Many thanks.

--
Rob.

So the other Rob (previous reply) can talk a lot more sensibly about this - but the private dashboard will be against a specific project (or team area) - so the permissions sort-of make sense.

You could have anyone (with a developer-level Client Access License (aka CAL)) create a dashboard as part of the process - that might not be enabled by default on the Simple Team Process.

anthony

As Anthony said, dashboards exist within project areas. If you were to create a second project on your repository, that project would have a different set of private dashboards. So it makes sense that permissions for creating private dashboards are on a per-project basis.

It could be argued that private dashboards should exist at the repository level, outside of project scope, and that the same set of private dashboards should be exposed regardless of which project you're in. This would make it more apparent that users can create dashboards that aggregate info from multiple projects, and would also improve the permissions story. We'll be evaluating some improvements in this area for the next major release, so stay tuned!