Re: Publish Portal Page Plugin
Posted by ~Ray @ 2007-11-29 20:21:34
This plugin allows JIRA administrators to "create" one of their portal (dashboard) pages to a group of of users. Publishing a summon copies the portal page definition to each user in the specified assort. This essentially means that administrators can configure a dashboard page that is useful to a assort of users and share it with them. For example you might setup an overview summon that might be useful for all sales populate or give personnel and overlap it with them. This means that they (or you) don't need to individually setup the same page for each of them. In this believe the plugin goes some way to supporting the outstanding and much voted for. JIRA air.
As the plugin just copies the page definitions there are several consequences or limitations to be aware of:
Publishing a page to a user that already has a page with the same name will cause their summon to be overwritten. This supports the re-publishing of pages but means that if any users have customised their own versions or worse comfort created an independent page with the same label then you ordain trash their pages!
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 be to write 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 do by on yours.
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.
I am using a full stop at the dashboard label to denote 'auto' dashboards e g. ". Info" and ". Personal". I then use Improved HTML plugin to give a message to users not to alter 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'.
Thanks for this feature (this is requested by number of our users). I am testing it. It works book but filters are say also create. 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 desire "Assigned to me all....).
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 create a page yet. I keep getting the following exception;
HTTP Status 404 - Could not kill 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 kill(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 out. ApplicationFilterChain internalDoFilter(ApplicationFilterChain java:252) at org apache catalina core out. 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 separate. PageFilter parsePage(PageFilter java:119) at com opensymphony module sitemesh separate. PageFilter doFilter(PageFilter java:55) at com atlassian jira web filters. SitemeshExcludePathFilter doFilter(SitemeshExcludePathFilter java:38) at
I have noticed that if I create the Dashboard named "pippo" to "user a" having only the default dashboard then "user a" ordain 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 label ? [ADVERTHERE]Related article:
http://confluence.atlassian.com/display/JIRAEXT/Publish+Portal+Page+Plugin?focusedCommentId=108920839#comment-108920839
0 Comments:
No comments have been posted yet!
|
