Hi guys,

We do appreciate the plugins being written and think they are filling a gap, but we will be writing this from scratched. The feature I have in mind is similar to Roman's though will be fully configurable via the UI. More importantly though, users will be able to search for pages they wish to include and add them to their dashboard. We will be introducing the concept of multiple share permissions (and extending filters to use this as well) and favourites (again, you will be able to favourite filters). We see filters a necessary piece of work for this issue due to so many portals being backed by filters (and we have been wanting to make filters easier to use for a long time anyway).
It should fully replace both plugins (sorry) and add a lot more functionality and usability on top.

As a bonus, for those using project roles, project admins will also be able to add dashboard pages to the the browse project page. I think will be awesome.

I totally agree with the pain of the ownership issues, though we still can't come up with an appropriate (easy) fix. Due to the time that this will take already, we decided not to make it part of this work.

Cheers for the input guys,
Nick

I haven't checked out Roman's plug in but if it "does what it says on the packet" it seems like a more elegant approach than mine and is more likely the way you'd want to implement the "proper" functionality.

Atlassian - I assume the sharing of portal pages would work in much the same way as sharing filters? If this is the case one thing worth considering is a couple of particular quirks of the shared filter approach that can be quite annoying that would be great not to bring across. The first issue is that an administrator can't delete someone else's filter and literally has to ask them to do this. Secondly, you can't transfer ownership of filters or have more than one owner. It's quite common to use a shared filter across a group and have that filter needing to be updated quite frequently. This causes a lot of issues when the specific owner is on leave/away etc. Although this perhaps doesn't sound like it would happen that often we've had it occur enough times to be painful and in these cases had to resort to modifying the underlying database directly to switch owners.

Anyway, hopefully these suggestions are useful!

Simon

Thanks Roman but I've installed your plugin but, after haivng followed your instructions for the installation, I dont see it in the plugins list under Administration. As a consequence, I can not share any dashboard, even if i have configured it.
I am running 3.11. Any incompatibility ? Any Idea ? A.

There is one more Jira plugin implemening this functionality. It already has first release candidate and seems to be stable and very usefull. The portal pages are NOT duplicated for every user like in Simon Keary's 'Publish Portal Page Plugin' but provides just view to your authored dashboards for other users. This feature provides possibility to update portal page by author and the updates are immediately visible by other users.

See http://code.google.com/p/jira-dashboard-sharing/

A quick question, only to understand where we are going. Is JIRA going to "take on board" the plugin developed by Simon Keary (Publish Portal Page Plugin) ?
Any other feature in mind then?

It would be great to have a kind of "short design description"? (maybe I am asking too much...but this feature is indeed very usefull).

As an example I have noticed that with the plug in developed by Simon, if I publish the Dashboard named "pippo" to "user a", having only the default dashboard, then "user a" will not have anymore the default dashboard but only a new Dashboard (only one) named "pippo". Can this be changed in the fact that published Dashboards are only "added" and never ovewrite the default one (or the ones configured by the user receiving the Dashboard) unless there is a Dashboard with the same name?

I created issue 14060 not realizing one already existed. I am linking it to this issue and hope this improvement will get on the road map as soon as possible.

This is now the most popular requested feature for JIRA. Any updates on the schedule?

Kind Regards,
Eric Salonen

Our needs and my suggestion are similar but different:
What we need is several dashboards. Same person needs two kinds of views: operational and statistical. And actually we have so much of statistics that we may need two of them.
So I would like to suggest having tabs for dashboards. You would automatically see all of the dashboards you have permissions to. And the tab order needs to be definable. Then we can have different default dashboard to different group or role.
Regular user could not change any of the dashboards. He could only take a private copy, create a new one (private) and select the order for his tabs.
This would mean that when we make changes to a dashboard it will affect everyone automatically and we don't need to watch out that we delete their custom settings.

Timo Riikonen
Accenture

Alternative, quick fix - please allow the admin to set the default dashboard as non-configurable.

I don't care if a user adds 50 new dashboards in addition to that, but I MUST have the default dashboard on all desktops so that I can get Announcements out and other key portlets.

Even now with 4 users on the system in development stage, its a pain in the butt to keep updating everyones default dashboards. God knows what it will be like when I have 200 people on it.

I really think this is a critical issue, more important than the work you've been doing recently on, for example, AJAX issue/user picker. The Dashboard is for us the 'Killer App' (or feature) that sold us on JIRA.

We too have hunreds of users, so this feature would be really great! Some users should only have a very simple view to lets say just any open issues in one certain project. The admin should be able to assign a configured dashboard to a group of users! Like I asked for in my forum entry here: http://forums.atlassian.com/thread.jspa?threadID=20594&tstart=0

Although the plug in probably is a useful stopgap, we have over 5000 users and our JIRA system is pivotal to our business and we hesitate from installing any plug ins.

Atlassian, given the sheer number of votes on this one feature plus the fact that the feature is soooo cool, i cannot understand why you have not started a feasibility study on this feature.

So please, add my vote

I've added the plugin to the library. See Publish Portal Page Plugin for further details.

Please let me know how it goes. I will try to fix up any issues quickly!

As mentioned on the plugin page please backup your database before trying out this plugin. You have been warned

Thanks,
Simon

Hi guys,

I got confirmation from Atlassian on the weekend that it's okay for me to put the plug-in source in the plug-in library. I'll do this in the next couple of days.

Regards,
SImon

Count me in with a copy as well please

Hi Simon,
when sharing the plugin privately, than please sen me one copy. We really need this feature.
Kind Regards
Sven

I would love a copy of the plugin.

-Eric (bloch at clearwellsystems dot com )

Simon,

Until we resolve the disclosure issue, could you please at least send privately the plugin to those interested ?

We definitely need it.

Cheers,
Aggelos

Hello,

I've created a basic plug-in that allows JIRA admins to copy one of their portal pages to a nominated group. This effectively clones the specified page for each user. Updating the page and then re-publishing it then replaces the previously cloned page with the updated one. Whilst the cloned pages are completely detached from the original, and can be edited by the users, it has been fairly useful in our team in allowing us to share certain pages. Hopefully this might also work as an interim solution for others?

I'm thinking of adding it to the JIRA plugins library but before doing this perhaps someone at Atlassian can answer the following query: As the plug-in is based on the in-built JIRA page clone functionality - and I've literally taken sections of the JIRA clone code and pasted them in my plugin source - is it okay to provide the source to the plug-in on Confluence?

Thanks and regards,
Simon Keary

Bonjour, je serai de retour le 24 Septembre 2007. Je ne peux pas lire votre e-mail pour le moment.

The aspect of sharing a dashboard is of most interest for us.

I don't know what you are cooking for 4.0, but I'm sure this feature will drive more customers to upgrade, and some new ones to commit One more vote from us.

Voted !!

This is one of those options that make our cliënts and users verry happy.
We create a nice dashboard for them so we can control a bit of what they see on their screens and they don't have to figure it out themselves anymore

It would be great if the dashboards can be shared across user accounts. We want to publish the dashboard to our execs. The only way to do this currently is to create a generic account and use it only for viewing the dashboard.

This feature would be very useful to us to create project-specific dashboards that everyone on the project could add to their personal dashboard.

For this reason, rather than share an entire dashboard, it would be good to be able to share a dashboard PAGE.

It might be even better to be able to TEMPLATE a dashboard page, so we could assemble a generic "<project> dashboard page" and have the user select the project when they add this page to their dashboard.

In my view JIRA portlets in Confluence are not usable. They require to put the login and password of a JIRA user in the URL.
The source of a page is available to anyone and thus the login and password of a user.

I understand that it is hard to choose, but this feature would really improve JIRA. Having some JIRA wizard setting up good dashboards with good filters and then letting the other users just add them as a desktop would really be great!

Perhaps Atlassian could try to give us more feedback on where this issue is placed with regards to version / priority?

Hi Leon,

The votes are not being ignored. In JIRA 3.9 we have implemented conversion of issues to subtasks - JRA-5410. We also implemented JRA-5617 and JRA-2367 which were both quite popular.

In JIRA 3.10 we are implementing JRA-2411 which is the 3rd most popular feature. In JIRA 3.10 we are also shipping JRA-1959.

Please note that when features are implemented, they stop being voted on, so the oldest issues always move towards the top.

Another thing to keep in mind is that while voting is important it is not the only contributing factor to the features we choose to implement next. For more information about how we choose to implement new features please see:
http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements

Having said all of the above, I would like to thank you for your feedback. Giving us information which shows which issues are important for you and why, does help us.

Cheers,
Anton

Hi Anton,

You say that there are a lot of popular feature requests, but this is curently the 4th most popular feature request so those of us that are following this issue are wondering what else exactly is taking precendence and why the voting seems to be being ignored?

Thanks,

Leon.

Hi,

Guys, unfortunately I do not have an implementation date for this feature. The reason is that there are a lot of popular feature requests, and we are trying our best to work through them. I am sorry for not being able to be more specific on time lines.

Cheers,
Anton

Personally, I got tired of configurig dashboards---and waiting for this feature. Check out JIRA Client by almworks. I have no need for this feature anymore.

Thanks,
Jeff

Hi... it's been a while since a comment from Atlassian... is there any update on this? I'm curious whether there's even a forecasted release # for this feature and if not, what other features/cleanup you need to develop to lay the groundwork for this, since it is your 4th most popular feature and I understand we're still a ways off from getting the #1 feature of field-level security permissions.

Looking forward to learning more about when we'd be able to:
a) share an existing dashboard for other individuals to optionally use
b) push a custom dashboard to appear as an added dashboard tab an entire team/group

Thanks!

I would definately like to see this feature implemented. It would make setting up new users soooooooo much easier!

along the sharing of a filter line of thought, being able to designate a page for sharing would be great. Then people could either include it in their dash or just click it somewhere.

Let me add my notes in support of this, from a chat with support...

• I have some nice portals setup so I can view the status of my project (as lead for a 5 person team). However, my team members cannot see the graphs that I create unless I login and show them.
• If I send snapshots, it is hard to print them. If I send links, the other people cannot see them. So, they do all of their checking by filter lists only, which loses a lot of the power of the application. Being able to share out a configured portal or dashboard would help a lot in synching up with team members, QA, etc.
• Comment: ok so they other membrs of the team should configure their dashboards with similar reports or filters
• Comment: dashboards are individual-specific
• I'm sure they could but it is kind of time-consuming. Filters start out individual-specific, but then can be shared out to projects or globally. I was hoping for something similar.

I look forward to using such a feature in the future...
Thanks,
Alan

Just duplicating many of the above request. We have business users that we need to set up. I'd like to:

1. Create the user
2. Setup their personal dashboard
3. Remove access to the default dashboard
4. Disallow the ability for the new user to change the personal dashboard layout

Thanks

+3 from the Confluence team

To those who have the chance to work with Confluence as well, there is a workaround while wating for this issue resolution : create wiki pages embedding jira portlets !

It's simple to do while requesting some discipline to make it deployable accross an organisation:
1- have a wiki technical user.
2- use it to create global filters
3- make a (candidate) jira dashboard page with these global filters
4- create a wiki page accessible to the people you want to share the same dashboard with.
5- add the jira portlet macro referencing the url of your candidate dashboard. Don't forget to add the wiki technical user name and pass if your Jira requires a logon

that's it !

It's not as performant as a pure Jira approach, but it's barely enough to cover the essential needs.

I hope this helps.

One more vote for this - I was just looking at creating release centric dashboards with portlets focussed on a particular project/release and it would be great to simply share these with the other developers involved.

adding the twohundredth vote on this issue.

This feature should bring much more effectivity to our work. It would be great for the users to share pre-defined statistics, charts etc.

Thanks in advance!

This is probably one of the most confusing things about JIRA – that I can't make views to share other than filters themselves. What is the status on this?

Thanks!

I agree to the above. My company is using Jira in distributed environment spread around the world in many timezones in the need for very different views and portals.

Hope you can please get this issue assigned and worked on.

This feature is urgently required by my team. We need external customers to have one dashboard (so that they can report issues and see the issues they have reported) and also NOT be able to change it (otherwise they will break it and... need to call support to get it fixed!) - then the support team themselves need another dashboard (to allow them to see new unassigned issues and all the issues assigned to them) - Developers could also benefit from having their own dash with some standard developer filters.

Also - when new customers or staff members come along, we need to be able to roll out a standard dash to them that we can train them on. We don't want to have to configure it by hand each time.

At the moment, our default dash has to be the dumbed-down customer-facing one, and all our internal staff need to configure their own additions to this.

We also need the ability to set up multiple default dashboards to choose from. We will soon be over 400 users. Please make this available as soon as possible.

Even in our small team this would be really useful. I've set up a fairly complicated dashboard, and would like to be able to share it with the rest of the team so they don't have to duplicate it. Please add this soon!

Hi all,
in our team we are working in distributed environment and this will be realy useful to share it among different sites.
Vlasta

I'm just feeling this point now...

It would be great it you could share out dashboard pages or configure the default dashboard to use multiple pages and permission them by group.

This would be nice to see - shared portal pages would also be good (not sure if only the first page in the list is the dashboard or not).

Being able to create special pages for particular contexts and sharing them with a group would give Jira a big jump in terms of its management abilities.

I can't agree more, for large dev teams where it is all about the stats, a shared dashboard or dashboard page would be great.

Can't it work just like filters? Make it so I can share my dashboard pages? I doesn't even have to be complete dashboards, just pages. Please... This would be so helpful for large deployments.

please allow simple sharing of dashboards soon. setting up a new team with multiple cross-project responsiblities is a royal pain in the neck.

In the spirit of agile development, permissions on sharing of dashboards, etc. can come later.

The basics first, please!

The first question almost everyone asked when I first showed them the Jira dashboards was how they could just copy mine, or if they could copy from a template dashboard that I created.

For the developers who tend to like to customize and tinker to get their dashboard just "perfect" there is at least one business person who just wants it to work and be done. This would be a great feature.

Thiago,

Unfortuantely I do not have an implementation date for this feature at the moment. Please, keep voting for this issue to show us that it is important to you.

Thanks,
Anton

We have almost 800 users and this feature would be really useful.
Most of users have similar functions.

Do you have any idea when it´s gonna be implemented?

Dashboards should also be linked to permissions so you can set who can view them and who can edit them.

I agree with Chris, this would be a very helpful feature to have if your development effort includes different roles.