| Name | Publish Portal Page Plugin |
|---|---|
| Version | 1.0 |
| Product Versions | 3.10.2 |
| Author(s) | Simon Keary |
| Homepage | |
| Price | FREE! |
| License | |
| JavaDocs | |
| IssueTracking | |
| Download JAR | immt-publishportal-jira-plugin-1.0.jar |
| Download Source | publish_portal_jira_plugin-1.0.zip |
Description/Features
This plugin allows JIRA administrators to "publish" one of their portal (dashboard) pages to a group of of users. Publishing a page copies the portal page definition to each user in the specified group.
This essentially means that administrators can configure a dashboard page that is useful to a group of users and share it with them. For example you might setup an overview page that might be useful for all sales people or support personnel and share it with them. This means that they (or you) don't need to individually setup the same page for each of them. In this regard the plugin goes some way to supporting the outstanding, and much voted for, JIRA issue JRA-2509.
As the plugin just copies the page definitions there are several consequences, or limitations to be aware of:
- If you publish a page and then update it you will need to re-publish it for users to see your updates.
- Each user that gets the publish page can update it. They can't publish their modified page, though, unless they are also admins.
- Publishing a page to a user that already has a page with the same name will cause their page to be overwritten. This supports the re-publishing of pages but means that if any users have customised their own versions, or worse still created an independent page with the same name, then you will trash their pages!
Note that I've built the plugin against the 3.10.2 JIRA development kit but from I think that it will probably support JIRA versions down to 3.8.x. I'm pretty sure that it won't support earlier versions, though, due to some changes in the JDK API.
Installation
Just copy the plugin, immt-publishportal-jira-plugin-1.0.jar, to the WEB-INF/lib directory and restart JIRA.
Usage
The "Publish Portal" operation is available under the administration menu under the "Users, Groups & Roles" section. Simply click "Portal", specify which page you want to copy and who you want to copy it to, and then click OK.
Please, Please, Please do backup your data before running this plugin! It works fine on our system but, until it's had wider testing, who knows what could go wrong on yours.
Version History
1.0 - Initial release
Screenshots
Screenshots |
|
|---|---|
|
|
Comments (9)
Oct 12, 2007
Marnix Uyttendaele says:
Hi Simon,\\ thanks for the plugin but, when I copy the jarfile to the server and...Hi Simon,
thanks for the plugin but, when I copy the jar-file to the server and restart Jira nothing happens not even an errormessage in the logfile
Keep in mind whe are running version 3.9.1 under Websphere 6.1, could that be the problem ?
Oct 22, 2007
mameha says:
Wonderful thank you for your effort\! Working for me on 3.9.2 standalone on winx...Wonderful - thank you for your effort! Working for me on 3.9.2 standalone on winxp.
Improvement Request: Users have to logout and login again. If they do not, they get an error when they click on the dashboard updated by this plugin.
Feature request: 'remove portal' from group X.
Usage Tip:
I am using a full stop at the dashboard name to denote 'auto' dashboards. e.g. ".Info" and ".Personal". I then use Improved HTML plugin to give a message to users not to edit the auto dashboards. I put announcements, tables of links to enterprise-wide useful saved filters, world time etc on ".Info" dashboard. The ".Personal" dashboard contains users 'assigned to me' and 'returned to me' and 'my watched issues'.
Oct 23, 2007
Abdelkader Boumediene says:
Hi Simon, Thanks for this feature (this is requested by number of our user...Hi Simon,
Thanks for this feature (this is requested by number of our users). I am testing it. It works fine but filters are note also publish. So I publish a Portla but it contains none result as filters not found.
So this could be used only if filters used use only Jira queries like "Assigned to me, all ....).
Regards
Nov 12, 2007
Nick Burn says:
Hi Simon, this is a great idea and I know I can gt a lot of use out of it, howev...Hi Simon, this is a great idea and I know I can gt a lot of use out of it, however I have not been able to successfully publish a page yet. I keep getting the following exception;
HTTP Status 404 - Could not execute action :<init><p><small><small><pre>java.lang.NoSuchMethodError: <init> at com.IMMT.jira.plugin.PublishPortalAction.createPortalPageConfiguration(PublishPortalAction.java:283) at com.IMMT.jira.plugin.PublishPortalAction.doExecute(PublishPortalAction.java:249) at webwork.action.ActionSupport.execute(ActionSupport.java:153) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:54) at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:132) at com.atlassian.jira.web.dispatcher.JiraServletDispatcher.service(JiraServletDispatcher.java:209) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.atlassian.jira.web.filters.AccessLogFilter.doFilter(AccessLogFilter.java:51) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(PageFilter.java:119) at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:55) at com.atlassian.jira.web.filters.SitemeshExcludePathFilter.doFilter(SitemeshExcludePathFilter.java:38) at
Any ideas?
Nov 29, 2007
Antonio Vollono says:
Simon, I have noticed that if I publish the Dashboard named "pippo" to "user a",...Simon,
I have noticed that 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 Dashbord (only one) named "pippo".
Can this be chnaged in the fact that published Dashboards are onle "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 ?
Jan 17, 2008
Andrew Eaton says:
I'd also love to see this add another dashboard page instead of replacing the de...I'd also love to see this add another dashboard page instead of replacing the default.
Mar 18
Alexey Serba says:
We've noticed the same behavior too. Agreed with Antonio. It would be great to n...We've noticed the same behavior too. Agreed with Antonio. It would be great to not overwrite the default dashboard.
May 02
Olle Friman says:
Hi Simon. We have recently updated to Jira 3.12.2 and we also included your plug...Hi Simon.
We have recently updated to Jira 3.12.2 and we also included your plugin for sharing dashboards. When I test the plugin in a test environment it worked fine, but now in production, when I try to share a dashboard, nothing happens. Everything looks ok...and I get the information that all went well, but no new dashboard tab appear for the receivers. Do you or someone else have a suggestion what could be wrong?
Thanks
Olle
Jun 22
Doods Perea says:
This plugin clashed with the JIRA Dashboard Sharing Plugin. As I was eager...This plugin clashed with the JIRA Dashboard Sharing Plugin. As I was eager to test it I completely removed the former (just disabling it won't work). I then followed the installation instruction here and did some tests and it worked on our JIRA 3.12.2. However, now I cannot manage my portal. In the Manage Portal page, I no longer see my previously created portals, although the form to create new ones is still there. But then when I create a new portal, the table that is supposed to list all my portals does not update. The weird thing is when I use the "Publish Portal" in Administration I see all the portals I have created (old and new) in the dropdown list.