You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@bloodhound.apache.org by Apache Bloodhound <bl...@incubator.apache.org> on 2012/05/28 18:51:28 UTC
[Apache Bloodhound] #93: Converting dashboard views to new template
#93: Converting dashboard views to new template
-------------------------+--------------------
Reporter: gjm | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: dashboard | Version:
Keywords: |
-------------------------+--------------------
We have had a new design for
dashboard/products/versions/milestones/components (and tickets) for a bit
and we could do with changing to the new form.
https://svn.apache.org/repos/asf/incubator/bloodhound/trunk/doc/html-
templates/product.html is the only fully converted reference template but
this specifies the general features that should be seen at each level.
Each of these views will have a list of tickets that focuses on the
specified level. The top level dashboard will show summary details of the
Products (when available), Versions, Milestones and Components. Each level
down will focus down, losing the summary of the level above (so Milestones
will be missing a list of Versions but will still have components).
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by gjm):
r1345273 adds an alternate unordered list mode to the cloud widget
I have set the unordered list mode to be the default for now and it may be
worth factoring out the common code.
Let me know what you think.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:10>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+-------------------------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: closed
Priority: major | Milestone: RC1 for initial release
Component: dashboard | Version:
Resolution: fixed | Keywords:
--------------------------+-------------------------------------
Changes (by gjm):
* status: accepted => closed
* resolution: => fixed
Comment:
Assuming this is up to date, I think that it is worth drawing a close to
this ticket. Any further associated work should go to new tickets.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:40>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by olemis):
Replying to [comment:10 gjm]:
> r1345273 adds an alternate unordered list mode to the cloud widget
>
> I have set the unordered list mode to be the default for now and it may
be worth factoring out the common code.
>
> Let me know what you think.
I'll take a look as soon as possible
''':)'''
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:11>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by gjm):
I'll have a proper look at this later but I like the idea of extending to
other rendering styles.
At some point it might be helpful to come up with a new name for the
widget now that we have subverted it's meaning to this extent.
Also, given that there is a default view, I would consider making the
<py:otherwise> match that default (probably with a comment to that effect)
rather than worry about catching that error. There may be more important
possible sources of error to concern ourselves with of course.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:14>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by olemis):
Changes suggested in [comment:ticket:93:14 this comment] and
[comment:ticket:93:6 this one] are implemented in
[attachment:t93_r1345273_comments_6_14_dashboard.diff this patch] . I also
submitted [attachment:t93_r1345273_widget_exc_upgrade.diff another patch]
that adds extra exception handling for widgets in order to render page
contents even if widget cannot be resolved by ID (e.g. provider component
disabled).
==== Dashboard ===
I tested everything with patches for #77 also applied in the following
order :
{{{
#!sh
$ hg qapplied
t93/t93_r1345273_ticket_field_cloud_mode_list.diff
t93/t93_r1345273_ticket_field_cloud_mode_table.diff
t93/t93_r1345273_ticket_field_cloud_mode_compact.diff
t93/t93_r1345273_ticket_field_cloud_badges.diff
t93/t93_r1345273_empty_count_ok.diff
t77/t77_r1345273_htdocs_locations_dashboard.diff
t77/t77_r1345273_bootstrap_2.0.4.diff
t77/t77_r1345273_btn_toolbar_radio.diff
t93/t93_r1345273_comments_6_14_dashboard.diff
t93/t93_r1345273_widget_exc_upgrade.diff
}}}
==== Theme ====
I tested everything with patches for #77 also applied in the following
order :
{{{
#!sh
$ hg qapplied
t77/t77_r1346147_theme_bootstrap.diff
t77/t77_r1346147_rm_bootstrap.diff
t77/t77_r1346147_htdocs_locations_theme.diff
t93/t93_r1346147_comments_6_14_theme.diff
}}}
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:16>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by olemis):
Some things to notice about current implementation of milestone view :
- There's no place for milestone owner in ''Trac''. In that case
Unassigned label is shown .
- If present milestone owner should be set in `milestone.owner`
(i.e. in template data).
- Bgcolor of progress bars changes according to the following rules
x < 33 => `progress-danger` ,
x >= 33 => `progress-warning` ,
x >= 66 => `progress-info` ,
x >= 100 => `progress-success`
- At present milestones have no keywords (cmiiw ''';)''' so that's
not visible now. I suggest to create a new ticket for this once
this will be ready.
- Should closed tickets be shown in milestone view ?
- Components cloud is more accurate now as statistics only consider
tickets scheduled for target milestone .
- Work for milestones is not finished yet. It still requires some
heavy work . Nonetheless I posted all these in advance so as to
get some feedback from you .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by gjm):
Actually, earlier I was playing with allowing the widget cloud to
optionally display as a simple list. I can commit a patch for that in a
few minutes.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:9>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+-------------------------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone: RC1 for initial release
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+-------------------------------------
Comment (by olemis):
Replying to [comment:33 gjm]:
> Replying to [comment:30 olemis]:
> > A decision needs to be made so as to choose between displaying only
ticket title or showing also date fields, reporter and owner information .
>
> I think we need to display more information in the sticky region
+1
> but we need to make sure that it is not too cluttered as well.
The [http://svn.apache.org/repos/asf/incubator/bloodhound/trunk/doc/html-
templates/ticket.html mockup] includes ticket fields as well , but I
didn't because it's possible to have a huge number of custom fields . If
this is the case that page will look a bit odd .
> What we have will probably do for now.
+1
> We can have a discussion about it on bh-dev at some point and raise new
tickets.
I look forward to this in order to develop further patches if needed .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:35>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by gjm):
As a quick hack, I have just been trying the following to modify the links
provided by the {{{TicketFieldValuesWidget}}} for lists of milestones so
that they go direct to the relevant page instead of the query.
{{{
#!diff
Index: bhdashboard/widgets/ticket.py
===================================================================
--- bhdashboard/widgets/ticket.py (revision 1351306)
+++ bhdashboard/widgets/ticket.py (working copy)
@@ -198,12 +198,18 @@
item_link= lambda item: query_href + \
'&' + urlencode([(fieldnm, item[0])])
+ def dash_item_link(item):
+ if fieldnm in ['milestone',] and item[0]:
+ return req.href(fieldnm, item[0])
+ else:
+ return item_link(item)
+
return 'widget_cloud.html', \
{
'title' : title,
'data' : dict(
bounds=minmax(items, lambda x: x[1]),
- item_link= item_link,
+ item_link= dash_item_link,
heading=_(fieldnm.capitalize()),
items=items,
verbose=verbose,
}}}
For completeness, the following adds a component list to the dashboard
page to demonstrate it working:
{{{
#!diff
Index: bhdashboard/web_ui.py
===================================================================
--- bhdashboard/web_ui.py (revision 1351315)
+++ bhdashboard/web_ui.py (working copy)
@@ -139,7 +139,7 @@
'div' : [
{
'_class' : 'span8',
- 'widgets' : [3, 2, 0]
+ 'widgets' : [3, 2, 0, 4]
},
{
'_class' : 'span4',
@@ -157,6 +157,14 @@
'field' : 'component',
'verbose' : True}}]
},
+ 4: {
+ 'args' : [
+ 'TicketFieldValues',
+ None,
+ {'args' : {
+ 'field' : 'milestone',
+ 'verbose' : True}}]
+ },
2: {
'args' : [
'TicketQuery',
}}}
It could probably do with referring to a mapping dictionary to get the
appropriate base link of course. I am sure there are other things that
could improve it but I was just scratching an itch.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:21>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by olemis):
Attached patches implement milestone view using continuous layout .
Approach was to do it step by step on top of
[attachment:ticket:65:t65_r1343875_milestone_sticky.diff sticky panels
patch] developed for #65, hence concatenating some minor enhancements to
bugs found along the way . In order to apply them please read instructions
below.
==== Theme plugin ====
Apply patches listed below (in that order) against r1343875 .
{{{
#!sh
$ hg qapplied
t65/t65_r1343875_milestone_sticky.diff
t93/t93_r1343875_continuous_milestone_header.diff
t93/t93_r1343875_continuous_milestone_widgets.diff
}}}
==== Dashboard plugin ====
Apply patches listed below (in that order) against r1343179 .
{{{
#!sh
$ hg qapplied
t93/t93_r1343179_fix_query_link.diff
t93/t93_r1343179_bootstrap_2.0.3.diff
t93/t93_r1343179_progress_bar_compact.diff
t93/t93_r1343179_ticket_query_cloud.diff
}}}
[attachment:t93_r1343179_bootstrap_2.0.3.diff Bootstrap version is
updated] . Nonetheless there's still more to do in that direction . Follow
#77 for further details.
After doing this , it now looks like shown in the following screenshot.
[[Image(bh_theme_x_35_milestone_continuous.png, width=600)]]
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by gjm):
r1351267 applies t93_r1345273_ticket_field_cloud_mode_list.diff
r1351281 applies t93_r1345273_ticket_field_cloud_mode_table.diff
r1351284 applies t93_r1345273_ticket_field_cloud_mode_compact.diff
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:17>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+-------------------------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone: RC1 for initial release
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+-------------------------------------
Comment (by olemis):
Attached patches implement progress bar in product view inside sticky
panels .
==== Dashboard ====
The [attachment:t93_r1352517_ticket_stats_widget_v2.diff patch for
dashboard plugin] implements ticket stats widget . It may be applied
directly against r1352517 .
==== Theme ====
Widget mentioned above has been tested by
[attachment:t93_r1352517_product_progress.diff embedding it in products
overview section] (i.e. sticky panel) . Patch has been developed against
r1352517 on top of previous patches applied in the following order.
{{{
#!sh
$ hg qapplied
t93/t93_r1352517_ticket_sticky.diff
t93/t93_r1352517_ticket_sticky_v2.diff
t93/t93_r1352517_product_progress.diff
}}}
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:34>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by jdreimann):
This is all good work, I'd just like to reiterate two points:
1. The template should equally apply to the Dashboard, Product, Version
and Milestone view at RC1.
1. The links to lower levels like components, projects and versions on the
[https://svn.apache.org/repos/asf/incubator/bloodhound/trunk/doc/html-
templates/product.html product template] don't have to show the full
status for now. A simple unordered list for each would be good enough for
RC1.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:8>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by gjm):
r1351314 applies t93_r1346147_milestone_widget_xml.diff
r1351315 applies t93_r1345273_dashboard_continuous.diff
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:20>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by olemis):
Replying to [comment:14 gjm]:
> I'll have a proper look at this later but I like the idea of extending
to other rendering styles.
>
> At some point it might be helpful to come up with a new name for the
widget now that we have subverted it's meaning to this extent.
>
+1
> Also, given that there is a default view, I would consider making the
<py:otherwise> match that default (probably with a comment to that effect)
rather than worry about catching that error
I'd do something equivalent . I suggest to set `view = 'list'` and display
a warning when `py:otherwise` applies
> There may be more important possible sources of error to concern
ourselves with of course.
we shall see ''';)'''
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:15>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+-------------------------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone: RC1 for initial release
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+-------------------------------------
Comment (by gjm):
Perhaps the product progress code is dependent on something else. I think
we need to provide a method for products to get the appropriate
information. Perhaps that should be a different ticket.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:36>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+-------------------------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone: RC1 for initial release
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+-------------------------------------
Comment (by gjm):
r1352880 adds a basic sticky panel for ticket view
r1352884 adds dates, reporter and owner fields to the sticky area
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:32>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by gjm):
Replying to [comment:3 olemis]:
> Some things to notice about current implementation of milestone view :
>
> - There's no place for milestone owner in ''Trac''. In that case
> Unassigned label is shown .
> - If present milestone owner should be set in `milestone.owner`
> (i.e. in template data).
Until a given part of the model has an owner (assuming that the milestone
ever will of course), it might be better to not show the unassigned label.
To make the solution general for all the models, can the difference
between a model lacking the field and actually being undefined be
determined?
> - Bgcolor of progress bars changes according to the following rules
> x < 33 => `progress-danger` ,
> x >= 33 => `progress-warning` ,
> x >= 66 => `progress-info` ,
> x >= 100 => `progress-success`
Happy with this for now. We might want to revisit this later but it is
likely to be a low priority visualisation task.
> - At present milestones have no keywords (cmiiw ''';)''' so that's
> not visible now. I suggest to create a new ticket for this once
> this will be ready.
Similarly to the discussion of ownership above - I will raise tickets for
both aspects.
> - Should closed tickets be shown in milestone view ?
I would say not. The link to the closed ticket query should suffice.
> - Components cloud is more accurate now as statistics only consider
> tickets scheduled for target milestone .
> - Work for milestones is not finished yet. It still requires some
> heavy work . Nonetheless I posted all these in advance so as to
> get some feedback from you .
I hope it was not too early to commit this work then!
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:6>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by gjm):
r1351288 applies t93_r1345273_ticket_field_cloud_badges.diff
r1351291 applies t93_r1345273_empty_count_ok.diff
r1351295 applies t93_r1345273_empty_count_ok_v2.diff
r1351302 applies t93_r1345273_comments_6_14_dashboard.diff (note temporary
breaking of milestones resolved by r1351303)
r1351303 applies t93_r1346147_comments_6_14_theme.diff
r1351304 applies t93_r1345273_widget_exc_upgrade.diff
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:18>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+-------------------------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone: RC1 for initial release
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+-------------------------------------
Comment (by olemis):
Product progress code is generic in the sense that it considers as input
any ticket query . It is rendered by ticket stats widget . The functions
needed to get this done are implemented in dashboard plugin . Considering
the fact that (so far) it's the right place to deliver reusable code (as
far as the bloodhound plugin family is concerned) I see two options :
1. Introduce a dependency between multiproduct plugin and dashboard
plugin .
2. Duplicate the code in dashboard plugin and include a copy in
multiproduct plugin .
IMO , in '''[2]''' code will be hard to maintain ...
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:37>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by gjm):
r1352216 applies t93_r1351761_generic_model_view.diff to add the generic
model template
I modified the approach taken in t93_r1351403_product_view.diff so that
we use the template overriding mechanism rather than changing the
multiproduct's product view template directly so that:
r1352218 applies t93_r1351403_product_view.diff and
t93_r1351761_milestone_model_view.diff to make milestone and product views
use the generic model template.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:29>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by olemis):
Attached patches implement a few more features explained below .
1. [attachment:t93_r1345273_ticket_field_cloud_mode_list.diff Suggested
enhancements] to gjm list view
2. Two new view modes :
[attachment:t93_r1345273_ticket_field_cloud_mode_table.diff table view]
and [attachment:t93_r1345273_ticket_field_cloud_mode_compact.diff compact
view]
3. [attachment:t93_r1345273_ticket_field_cloud_badges.diff Highlight
ticket count] in verbose mode using
[http://twitter.github.com/bootstrap/components.html#badges bootstrap
badges]
4. [attachment:t93_r1345273_empty_count_ok.diff Use COALESCE in SQL
query] in order to obtain correct ticket count for ''empty'' category
(i.e. tickets with target field not set).
They should be applied against r1345273 in the following order :
{{{
#!sh
$ hg qapplied
t93/t93_r1345273_ticket_field_cloud_mode_list.diff
t93/t93_r1345273_ticket_field_cloud_mode_table.diff
t93/t93_r1345273_ticket_field_cloud_mode_compact.diff
t93/t93_r1345273_ticket_field_cloud_badges.diff
t93/t93_r1345273_empty_count_ok.diff
}}}
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:13>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Changes (by olemis):
* owner: nobody => olemis
* status: new => accepted
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+-------------------------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone: RC1 for initial release
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+-------------------------------------
Changes (by olemis):
* milestone: => RC1 for initial release
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:31>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by olemis):
It's ok . Feel free to commit this as well .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:22>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+-------------------------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone: RC1 for initial release
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+-------------------------------------
Comment (by gjm):
r1354926 applies ticket_stats_widget_v2.diff
r1354927 applies product_progress.diff
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:38>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by gjm):
Further patches appear to require #45 to be completed.. investigating.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:19>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by gjm):
Note the change in ticket:36#comment:1 to the buttons.
Looking good though!
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:5>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+-------------------------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone: RC1 for initial release
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+-------------------------------------
Comment (by gjm):
So, I misunderstood how that worked for a while
Replying to [comment:37 olemis]:
> Product progress code is generic in the sense that it considers as input
any ticket query . It is rendered by ticket stats widget . The functions
needed to get this done are implemented in dashboard plugin . Considering
the fact that (so far) it's the right place to deliver reusable code (as
far as the bloodhound plugin family is concerned) I see two options :
>
> 1. Introduce a dependency between multiproduct plugin and dashboard
plugin .
> 2. Duplicate the code in dashboard plugin and include a copy in
multiproduct plugin .
>
> IMO , in '''2''' code will be hard to maintain ...
I only meant that I thought we would need an ITicketGroupStatsProvider
implementation or something similar for products. I don't see a need for
the dependency or code duplication on this basis.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:39>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by gjm):
r1351761 uses field values widget to show milestones and versions; only
shows the heading for the widget if the title is missing; provides a
mechanism to specify an object link instead of a query link.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:27>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by gjm):
r1345105 and r134511 converts widgets for the milestone to continuous
style
r1345116 fixes the query link
r1345119 updates the dashboard's bootstrap css
r1345124 compact view for progress bars
r1345132 updates support for TracQuery language in widget cloud
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:4>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by olemis):
Finally I could make multiproduct plugin work ... yeehaw ! (... thnx
[query:status=!closed&reporter=gjm gjm] ...)
[attachment:t93_r1351761_generic_model_view.diff Attached patch for
dashboard] provides a generic template for model views . The other two
update milestone view , and upgrade product pages to insert widgets and
sticky panels in there . They should be applied against r1351761
('''dashboard''') , r1351403 ('''multiproduct''') and r1351761
('''theme''') respectively .
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:28>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by olemis):
Replying to [comment:24 gjm]:
> Replying to [comment:23 olemis]:
> > Replying to [comment:21 gjm]:
> > > As a quick hack, I have just been trying the following to modify the
links provided by the {{{TicketFieldValuesWidget}}} for lists of
milestones so that they go direct to the relevant page instead of the
query.
> > >
> >
> > Though I think it will be better this way ...
> >
> [snip]
> > You know , something like that . The idea is avoid calling `item_link`
inside `dash_item_link` . The `if` statement and associated check should
also be redundant . Hence that way it should be more efficient . Further
enhancements still possible ''';)'''
>
> Possibly, although one of the {{{item_link}}} calls was for the empty
{{{item[0]}}} and so I was providing the query link for that. Of course,
that might be a surprise to be using a different view. The redirect to the
roadmap in the case of {{{path/to/env/milestone/}}} is not particularly
helpful here. It feels like we should have some kind of milestone display
for tickets that are not in any milestone though. Perhaps we can provide
such views on {{{path/to/env/dashboard/milestone/}}} somehow.
>
IMO . If milestone is not empty then show link to milestone , otherwise
insert link to query for empty milestone . What d'u think ?
> Also, it might be worth providing a dictionary with the dashboard links
so that we do not need to guarantee that the links are always of the form
{{{path/to/env/fieldnm/item[0]}}} as the above suggests. We could use
something like:
> {{{
> #!python
> DASH_ITEM_HREF_MAP = {'milestone': ('dashboard','milestone',)}
> }}}
>
> which could be translated to a path with:
> {{{
> #!python
> def dash_item_link(item):
> args = self.DASH_ITEM_HREF_MAP[fieldnm] + (item[0],)
> return req.href(*args)
> }}}
>
hmmm ... if this is the case , I'll provide a suggestion in a while
''';)'''
> By the way, is there a particular reason for the numeric keys in the
{{{DASHBOARD_SCHEMA['widgets']}}} dictionary?
Any key should work , it just needs to match those specified for widgets
specs ''';)'''
> I'm tempted to change those to descriptive names so that I can specify
the set of widgets as
>
> {{{
> #!python
> ['my tickets', 'active tickets', 'milestones', 'components']
> }}}
+1
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:25>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by gjm):
Replying to [comment:23 olemis]:
> Replying to [comment:21 gjm]:
> > As a quick hack, I have just been trying the following to modify the
links provided by the {{{TicketFieldValuesWidget}}} for lists of
milestones so that they go direct to the relevant page instead of the
query.
> >
>
> Though I think it will be better this way ...
>
[snip]
> You know , something like that . The idea is avoid calling `item_link`
inside `dash_item_link` . The `if` statement and associated check should
also be redundant . Hence that way it should be more efficient . Further
enhancements still possible ''';)'''
Possibly, although one of the {{{item_link}}} calls was for the empty
{{{item[0]}}} and so I was providing the query link for that. Of course,
that might be a surprise to be using a different view. The redirect to the
roadmap in the case of {{{path/to/env/milestone/}}} is not particularly
helpful here. It feels like we should have some kind of milestone display
for tickets that are not in any milestone though. Perhaps we can provide
such views on {{{path/to/env/dashboard/milestone/}}} somehow.
Also, it might be worth providing a dictionary with the dashboard links so
that we do not need to guarantee that the links are always of the form
{{{path/to/env/fieldnm/item[0]}}} as the above suggests. We could use
something like:
{{{
#!python
DASH_ITEM_HREF_MAP = {'milestone': ('dashboard','milestone',)}
}}}
which could be translated to a path with:
{{{
#!python
def dash_item_link(item):
args = self.DASH_ITEM_HREF_MAP[fieldnm] + (item[0],)
return req.href(*args)
}}}
By the way, is there a particular reason for the numeric keys in the
{{{DASHBOARD_SCHEMA['widgets']}}} dictionary? I'm tempted to change those
to descriptive names so that I can specify the set of widgets as
{{{
#!python
['my tickets', 'active tickets', 'milestones', 'components']
}}}
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:24>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+-------------------------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone: RC1 for initial release
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+-------------------------------------
Comment (by gjm):
Replying to [comment:30 olemis]:
> A decision needs to be made so as to choose between displaying only
ticket title or showing also date fields, reporter and owner information .
I think we need to display more information in the sticky region but we
need to make sure that it is not too cluttered as well. What we have will
probably do for now. We can have a discussion about it on bh-dev at some
point and raise new tickets.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:33>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by olemis):
Replying to [comment:21 gjm]:
> As a quick hack, I have just been trying the following to modify the
links provided by the {{{TicketFieldValuesWidget}}} for lists of
milestones so that they go direct to the relevant page instead of the
query.
>
Though I think it will be better this way ...
{{{
#!diff
Index: bhdashboard/widgets/ticket.py
===================================================================
--- bhdashboard/widgets/ticket.py (revision 1351306)
+++ bhdashboard/widgets/ticket.py (working copy)
@@ -198,12 +198,18 @@
item_link= lambda item: query_href + \
'&' + urlencode([(fieldnm, item[0])])
+ def dash_item_link(item):
+ if item[0]:
+ return req.href(fieldnm, item[0])
+
return 'widget_cloud.html', \
{
'title' : title,
'data' : dict(
bounds=minmax(items, lambda x: x[1]),
- item_link= item_link,
+ item_link= dash_item_link if fieldnm in
('milestone',) else item_link,
heading=_(fieldnm.capitalize()),
items=items,
verbose=verbose,
}}}
You know , something like that . The idea is avoid calling `item_link`
inside `dash_item_link` . The `if` statement and associated check should
also be redundant . Hence that way it should be more efficient . Further
enhancements still possible ''';)'''
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:23>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by gjm):
Replying to [comment:25 olemis]:
>
> IMO . If milestone is not empty then show link to milestone , otherwise
insert link to query for empty milestone . What d'u think ?
It will do for now I think. It will be an inconsistency though. Also I
think it should call the lambda to get the appropriate query until we have
a better solution.
> hmmm ... if this is the case , I'll provide a suggestion in a while
''';)'''
OK, if your suggestion comes after anything I commit then we can look at
it again.
> > I'm tempted to change those to descriptive names so that I can specify
the set of widgets as
> >
> > {{{
> > #!python
> > ['my tickets', 'active tickets', 'milestones', 'components']
> > }}}
>
> +1
Cool, then that will go in too.
I'll also include a small quick change so that if a title is provided, the
heading is not provided. Incidentally, I think without a title, the empty
{{{<H3/>}}} is giving an artificial extra area above each of the value
widgets which would probably be better to remove. I suspect we could match
the spacing suggested by the designs by other means.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:26>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by olemis):
Replying to [comment:8 jdreimann]:
> This is all good work, I'd just like to reiterate two points:
> 1. The template should equally apply to the Dashboard, Product, Version
and Milestone view at RC1.
understood . Like I said before I just shared those patches in order to
get some feedback . Considering the fact that getting all these done with
a single template might need a generic solution , and I still don't see
how everything fits in its own place, then I decided to move forward step
by step and see how solution evolves as we add additional models in the
hierarchy.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:12>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by gjm):
#95 and #96 cover generic model dependent display of owner and keywords
data respectively.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:7>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
Re: [Apache Bloodhound] #93: Converting dashboard views to new template
Posted by Gary Martin <ga...@wandisco.com>.
Hi,
As Joe provided the changed design some time ago, this change may be a
little overdue. Comments and any requests for clarification would be useful.
Cheers,
Gary
On 05/28/2012 05:51 PM, Apache Bloodhound wrote:
> #93: Converting dashboard views to new template
> -------------------------+--------------------
> Reporter: gjm | Owner: nobody
> Type: enhancement | Status: new
> Priority: major | Milestone:
> Component: dashboard | Version:
> Keywords: |
> -------------------------+--------------------
> We have had a new design for
> dashboard/products/versions/milestones/components (and tickets) for a bit
> and we could do with changing to the new form.
>
> https://svn.apache.org/repos/asf/incubator/bloodhound/trunk/doc/html-
> templates/product.html is the only fully converted reference template but
> this specifies the general features that should be seen at each level.
>
> Each of these views will have a list of tickets that focuses on the
> specified level. The top level dashboard will show summary details of the
> Products (when available), Versions, Milestones and Components. Each level
> down will focus down, losing the summary of the level above (so Milestones
> will be missing a list of Versions but will still have components).
>
Re: [Apache Bloodhound] #93: Converting dashboard views to new
template
Posted by Apache Bloodhound <bl...@incubator.apache.org>.
#93: Converting dashboard views to new template
--------------------------+----------------------
Reporter: gjm | Owner: olemis
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by olemis):
I'm ok with [comment:ticket:93:29 your decision] .
OTOH , attached patches should be applied in the order shown below against
r1352517 in order to introduce sticky panels in enhanced ticket view . The
second patch is optional . A decision needs to be made so as to choose
between displaying only ticket title or showing also date fields, reporter
and owner information .
{{{
#!sh
$ hg qapplied
t93/t93_r1352517_ticket_sticky.diff
t93/t93_r1352517_ticket_sticky_v2.diff
}}}
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/93#comment:30>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker