Names for queries/reports sounds reasonable. It is interesting to think
how we might deal with providing wiki links for per-user defined queries.
I don't think that we should be repurposing the Reports section, rather
we should be expanding the purpose. That the page is there to provide
links to lists of tickets is fine. To be able to have graphical
representations of this data, with potentially arbitrary x and y axes
would be great as well. It would also be useful to be able to have
reports that allow the setting of a variable, say for specifying a month
so that you can use a single report to generate monthly reporting.
Working on improving reports sounds like it is going to be a whole lot
of fun!
Cheers,
Gary
On 16/10/12 07:27, Peter Koželj wrote:
I would go even further. Beyond pinning, user should be able to name and
change them.
Actually if we look at the report as they currently are that is almost
exactly what we need, but reports should be more than that...
On Mon, Oct 15, 2012 at 3:17 PM, Joachim Dreimann <
[email protected]> wrote:
Yep, that's a thought. I'm also thinking users should be able to 'pin' or
'favourite' queries if they so choose so that they stay available on the
page.
That would give us the freedom to repurpose the Reports section to
something more like a report: Reporting (over time) on progress /
objectives / activity. That's something for a different ticket of course.
- Joe
On 15 October 2012 13:24, Gary Martin <[email protected]> wrote:
On 15/10/12 13:10, Apache Bloodhound wrote:
#230: On custom query screen, show recent queries by the users
--------------------------+---**-----------------------
Reporter: jdreimann | Owner: nobody
Type: enhancement | Status: new
Priority: major | Milestone:
Component: ui design | Version:
Resolution: | Keywords: custom query
--------------------------+---**-----------------------
Changes (by jdreimann):
* keywords: => custom query
Old description:
,, ... via ''Bloodhound'' quick create ticket dialog,,
New description:
This could be the three most recent queries by the user for example.
From a design perspective, this could simply show a list of links to
those
queries at the top of the Custom Query screen:
{{{
#!html
<h4>Most recent queries</h4>
<ol>
<li><a href="">Milestone: Release 2, Owner: gjm, Status:
!closed</a></li>
<li><a href="">Owner: jdreimann, Status: !closed</a></li>
<li><a href="">Due date: > today </a></li>
</ol>
}}}
--
Ticket URL:<https://issues.apache.
**org/bloodhound/ticket/230#**comment:1<
https://issues.apache.org/bloodhound/ticket/230#comment:1>
Quite a nice idea. Any thoughts about providing a longer history
available
somewhere?
Cheers,
Gary
