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 2013/03/18 18:41:19 UTC
[Apache Bloodhound] Proposals/BEP-0004 modified
Page "Proposals/BEP-0004" was changed by olemis
Diff URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0004?action=diff&version=22>
Revision 22
Comment: bep:0004 list tickets using widgets (see #138) ... our own dog's food ;)
Changes:
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: Proposals/BEP-0004
=========================================================================
--- Proposals/BEP-0004 (version: 21)
+++ Proposals/BEP-0004 (version: 22)
@@ -123,11 +123,11 @@
=== Beta phase #beta
Next release (Beta phase) should concentrate on code stability and the following features:
-[[TicketQuery(keywords=~bep-0004-beta, format=table, col=id|summary|status|owner|milestone)]]
+[[Widget(TicketQuery, query="keywords=~bep-0004-beta&col=id&col=summary&col=status&col=owner&col=milestone", title=Ticket summary beta phase)]]
=== Stable phase
Solution should be stable enough to be part of Bloodhound standard delivery and replace existing search functionality. We can add more features
-[[TicketQuery(keywords=~bep-0004-stable, format=table, col=id|summary|status|owner|milestone)]]
+[[Widget(TicketQuery, query="keywords=~bep-0004-stable&col=id&col=summary&col=status&col=owner&col=milestone", title=Ticket summary stable phase)]]
Other possible features
* More complex faceting can be introduced e.g. date rages, pivot faces etc.
-------8<------8<------8<------8<------8<------8<------8<------8<--------
--
Page URL: <https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0004>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker
This is an automated message. Someone added your email address to be
notified of changes on 'Proposals/BEP-0004' page.
If it was not you, please report to .
Re: [Apache Bloodhound] Proposals/BEP-0004 modified
Posted by Joachim Dreimann <jo...@wandisco.com>.
On 19 March 2013 07:21, Olemis Lang <ol...@gmail.com> wrote:
> On 3/18/13, Ryan Ollos <ry...@wandisco.com> wrote:
> > On Mon, Mar 18, 2013 at 10:41 AM, Apache Bloodhound <
> > bloodhound-dev@incubator.apache.org> wrote:
> >
> [...]
> >
> >
> > Cool! Is there a way to color by status,
>
> no ...
>
> > or show closed tickets in
> > strike-through, or some other good indicator of ticket status?
>
> no ...
>
> > Appending
> > "&group=status" gives the status on the lhs of the table, but there is
> > probably a better way.
> >
>
> both «no» above are intentional and by design .
>
> @jdreimann : I do not recall now whether strike-through would be
> desired / tolerated . I do recall colors were rejected at least until
> we have consensus on #67
>
Strikethrough of the ticket ID for closed tickets is a good idea I think.
Ticket #67 was decided with comment:11 I reckon: Ready to implement anyway
and others can improve it later via commits rather than raising tickets
since it's such a trivial issue.
https://issues.apache.org/bloodhound/ticket/67#comment:11
- Joe
> @rjollos : ... yeah , so long and no final decision on that subject .
>
> --
> Regards,
>
> Olemis.
>
--
Joe Dreimann
UX Designer | WANdisco <http://www.wandisco.com/>
Re: [Apache Bloodhound] Proposals/BEP-0004 modified
Posted by Olemis Lang <ol...@gmail.com>.
On 3/18/13, Ryan Ollos <ry...@wandisco.com> wrote:
> On Mon, Mar 18, 2013 at 10:41 AM, Apache Bloodhound <
> bloodhound-dev@incubator.apache.org> wrote:
>
[...]
>
>
> Cool! Is there a way to color by status,
no ...
> or show closed tickets in
> strike-through, or some other good indicator of ticket status?
no ...
> Appending
> "&group=status" gives the status on the lhs of the table, but there is
> probably a better way.
>
both «no» above are intentional and by design .
@jdreimann : I do not recall now whether strike-through would be
desired / tolerated . I do recall colors were rejected at least until
we have consensus on #67
@rjollos : ... yeah , so long and no final decision on that subject .
--
Regards,
Olemis.
Re: [Apache Bloodhound] Proposals/BEP-0004 modified
Posted by Ryan Ollos <ry...@wandisco.com>.
On Mon, Mar 18, 2013 at 10:41 AM, Apache Bloodhound <
bloodhound-dev@incubator.apache.org> wrote:
> Page "Proposals/BEP-0004" was changed by olemis
> Diff URL: <
> https://issues.apache.org/bloodhound/wiki/Proposals/BEP-0004?action=diff&version=22
> >
> Revision 22
> Comment: bep:0004 list tickets using widgets (see #138) ... our own dog's
> food ;)
> Changes:
> -------8<------8<------8<------8<------8<------8<------8<------8<--------
> Index: Proposals/BEP-0004
> =========================================================================
> --- Proposals/BEP-0004 (version: 21)
> +++ Proposals/BEP-0004 (version: 22)
> @@ -123,11 +123,11 @@
>
> === Beta phase #beta
> Next release (Beta phase) should concentrate on code stability and the
> following features:
> -[[TicketQuery(keywords=~bep-0004-beta, format=table,
> col=id|summary|status|owner|milestone)]]
> +[[Widget(TicketQuery,
> query="keywords=~bep-0004-beta&col=id&col=summary&col=status&col=owner&col=milestone",
> title=Ticket summary beta phase)]]
>
> === Stable phase
> Solution should be stable enough to be part of Bloodhound standard
> delivery and replace existing search functionality. We can add more features
> -[[TicketQuery(keywords=~bep-0004-stable, format=table,
> col=id|summary|status|owner|milestone)]]
> +[[Widget(TicketQuery,
> query="keywords=~bep-0004-stable&col=id&col=summary&col=status&col=owner&col=milestone",
> title=Ticket summary stable phase)]]
>
> Other possible features
> * More complex faceting can be introduced e.g. date rages, pivot faces
> etc.
> -------8<------8<------8<------8<------8<------8<------8<------8<--------
>
Cool! Is there a way to color by status, or show closed tickets in
strike-through, or some other good indicator of ticket status? Appending
"&group=status" gives the status on the lhs of the table, but there is
probably a better way.