I'm not sure what you mean by "changes made to the default dashboard by
the admin are not propagated to the user's dashboard". They are separate
dashboards, so why should changes to one affect the other?

Are you asking for a sort of 'inheritable dashboard' feature? How would
changes to the original be 'merged' in with changes the user may have
made to their dashboard?

Cheers,
Jeff

–
ATLASSIAN - http://www.atlassian.com
Expert J2EE Software, Services and Support
jira-support@atlassian.com ICQ: 326266423
JIRA Docs: http://www.atlassian.com/software/jira/docs/latest

Thanks for the quick reply. I'll clarify what I am getting to in sample
scenario.

1. JIRA Administrator changes the default dashboard to suit the
company's needs. Not the one in their personal profile but the one
accessible via Administration - Global Settings - Default dashboard.

2. New employee XYZ joins the company and they are created a JIRA
account.

3. When XYZ logs in for the first time they are presented with the
default dashboard the Administrator created in Step 1.

4. Administrator decides the default dashboard needs to be updated and
makes changes to the default dashboard.

5. User XYZ logs in to JIRA and sees the updated dashboard.

That's the default behaviour I have observed so far, it's great. I'll
refer to this behaviour as 'inherited dashboard'.

Here is situation where the inherited dashboard would be a good thing to
have but doesn't seem to work that way.

1. As above user XYZ has default untouched dashboard and decides to add
some project specific dashboards. They do this via their home page, they
click on Manage Portal and they choose to add a new portal page called
Project123. Their homepage now has 2 tabs, Dashboard and Project123.

2. Administrator makes changes to the default dashboard.

3. User XYZ logs in, their default dashboard is not updated, they have a
snapshot copy of the default dashboard when they created the Project123
portal page. 'inherited dashboard' behaviour no longer applies.

My suggestion is to keep 'inherited dashboard' for users with multiple
portal pages. We find it would be useful as it lets everybody access a
standard page while allowing customisation, best of both worlds.

I hope that makes it clear enough, if there are any questions please
feel free to call me.

Regards,

Baris Yaroglu
eBusiness Consultant | CustomWare Asia Pacific | www.customware.net
T: +61-2-9900-5700 | F: +61-2-9475-0100 | M: +61-416-080-100
Improve the quality of your services with WmUnit
Unit testing framework for WebMethods http://www.customware.net/wmunit

----Original Message----
From: Jeff Turner (JIRA) jira@atlassian.com
Sent: Tuesday, 11 January 2005 4:28 PM
To: baris@customware.net
Subject: [JIRA] Commented: (JRA-5615) Allow default dashboard pages to
be updated when multi portlet pages are used.

[
http://jira.atlassian.com/browse/JRA-5615?page=comments#action_29384 ]

Jeff Turner commented on JRA-5615:
----------------------------------

Hi,

I'm not sure what you mean by "changes made to the default dashboard by
the admin are not propagated to the user's dashboard". They are
separate
dashboards, so why should changes to one affect the other?

Are you asking for a sort of 'inheritable dashboard' feature? How would
changes to the original be 'merged' in with changes the user may have
made to their dashboard?

Cheers,
Jeff

–
ATLASSIAN - http://www.atlassian.com
Expert J2EE Software, Services and Support
jira-support@atlassian.com ICQ: 326266423
JIRA Docs: http://www.atlassian.com/software/jira/docs/latest

are used.
------------------------------------------------------------------------
------

feature. There is also another useful feature to have multiple portal
pages on the home screen. This way each user can keep their own page as
well as the standard page for the company. We've noticed that when a
user is using more than 1 page on their home screen, changes made to the
default dashboard by the admin are not propagated to the user's
dashboard. This leaves the users with static dashboard pages, I
think they would be much more functional if they were still referenced
and updated by the admin.

–
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.atlassian.com/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira

Thanks for the report; this will come up in our next version planning meeting.

Regards,

Baris Yaroglu
eBusiness Consultant | CustomWare Asia Pacific | www.customware.net
T: +61-2-9900-5700 | F: +61-2-9475-0100 | M: +61-416-080-100
Improve the quality of your services with WmUnit
Unit testing framework for WebMethods http://www.customware.net/wmunit

----Original Message----
From: Jeff Turner (JIRA) jira@atlassian.com
Sent: Thursday, 13 January 2005 2:36 PM
To: baris@customware.net
Subject: [JIRA] Commented: (JRA-5615) Allow default dashboard pages to
be updated when multi portlet pages are used.

[
http://jira.atlassian.com/browse/JRA-5615?page=comments#action_29474 ]

Jeff Turner commented on JRA-5615:
----------------------------------

Thanks for clarifying - I see what you mean (the "Dashboard" page is
actually a copy, not the default). It would be better if JIRA only
copied the default dashboard when the user first modifies it, so it
inherits otherwise.

Thanks for the report; this will come up in our next version planning
meeting.

This is not by deisgn as such, but a limitation of JIRA that we are hoping to address in the future.

Thanks,
Anton