On 11/29/05, Ross Gardler <[EMAIL PROTECTED]> wrote: > David Crossley wrote: > > Ross Gardler wrote: > > > >>Do we have control over what appears on the home page, I'll take a look > >>in half an hour or so and see if I can make any suggestions. > > > > > > I am no Jira expert, but i gather that we can define our > > own "screens" and over-ride defaults, etc. Good luck. > > I cannot find a way of changing the default screen, it only appears > possible to configure screens that deal with individual issues. The JIRA > docs don't help either.
I understand the default screen to be the "Default Dashboard". In any case, we can't change it specific to a project apparently -- it can either be changed globally or for individual users. > The only way I can see of addressing this within JIRA is to create > projects for each of the plugins and make them a part of the Forrest > group. This seems like way too much overhead at this stage in the project. I agree. > A workaround would be to create our own report page using the > projectInfo plugin. This would replace the page we have that links to > the issue tracker at present [1]. This would then include direct links > to create a new issue and a set of specific searches, such as important > issue in core, issues scheduled for the next release, blockers across > the whole project etc. > > to do this we need to: > > - create the page to appear in our site (in projectInfo) > - create the reports we want to produce (in Jira) > - create the XSL to convert the JIRA XML to XDoc > - add the processing to projectInfo plugin > > I think that we are getting to the point of making this work worthwhile. > It is certainly in line with the original goals of Forrest and would be > very useful across Apache as a whole (especially if we leverage the > possibility of creating lists of Apache projects). > > It also has the advantage that we won't be sending people away from our > site to see the proposed roadmap and known important issues. > > What do people think? Shall we create an issue for this and work on it > when we can? Since we'll always have users going to JIRA and seeing the main dashboard page, I think we ought to bring our question up to Atlassian or Infra and see if there is a good solution already out there first. Otherwise, we're going to have our "real" view of the project/issues on our issues page but others will be using JIRA. Heck, maybe no one minds us creating a new JIRA portlet and changing up the default dashboard. --tim
