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 <de...@bloodhound.apache.org> on 2013/10/04 19:30:44 UTC
[Apache Bloodhound] #687: Clean up ticket timeline - arrow line and
grouping of events
#687: Clean up ticket timeline - arrow line and grouping of events
--------------------------+---------------
Reporter: gjm | Owner:
Type: enhancement | Status: new
Priority: major | Version:
Resolution: |
--------------------------+---------------
This is to continue the work of #471 and #473. #471 in particular shows
mockups where there are indications of the direction of time in the arrow
and methods of drawing attention to changes that were made in a single
update.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/687>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #687: Clean up ticket timeline - arrow line
and grouping of events
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#687: Clean up ticket timeline - arrow line and grouping of events
--------------------------+----------------------
Reporter: gjm | Owner: gjm
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Comment (by gjm):
r1529237 replaces the arrow of time and highlights groups of events that
were posted together
The above includes:
* a change from no display until mouse over to partial transparency for
the extra entry information (date and or author information) to avoid
geometry changes
* a change to the sticky header due to a strange rendering issue of the
css timeline - the slight opacity seems to fix but seems rather wrong
* dropping the width specification on the anonymous submission
information to improve the rendering of this
I would additionally like to see some more sense made of the extra
information for logically associated changes as of course the date and
user will be the same for all of them; appearing in one location that
looks as though it is associated may well be better than the odd
transparency I have given them for now.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/687#comment:2>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #687: Clean up ticket timeline - arrow line
and grouping of events
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#687: Clean up ticket timeline - arrow line and grouping of events
--------------------------+-----------------------
Reporter: gjm | Owner: gjm
Type: enhancement | Status: closed
Priority: major | Milestone: Release 8
Component: dashboard | Version:
Resolution: fixed | Keywords:
--------------------------+-----------------------
Changes (by gjm):
* status: accepted => closed
* resolution: => fixed
* milestone: => Release 8
Comment:
Optimistically closing as fixed.
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/687#comment:3>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
Re: [Apache Bloodhound] #687: Clean up ticket timeline - arrow line
and grouping of events
Posted by Apache Bloodhound <de...@bloodhound.apache.org>.
#687: Clean up ticket timeline - arrow line and grouping of events
--------------------------+----------------------
Reporter: gjm | Owner: gjm
Type: enhancement | Status: accepted
Priority: major | Milestone:
Component: dashboard | Version:
Resolution: | Keywords:
--------------------------+----------------------
Changes (by gjm):
* status: new => accepted
* owner: => gjm
* component: => dashboard
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/687#comment:1>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker