On Tue, Mar 10, 2015 at 4:37 PM, jungle Boogie <jungleboog...@gmail.com>
wrote:
>
> On 10 March 2015 at 12:15, Ron W <ronw.m...@gmail.com> wrote:
> > Many issue tracking systems have a GUI, "point and click" query
> > builder/editor. So, SQL use can be mostly avoided.
> >
> > Creating such a query builder (probably in Javascript) for Fossil might
> be a
> > good idea.
>
> Not diminishing your recommendation at all because it probably would
> be helpful, but because there's not a builder in place, it enables so
> much more than whoever creates the builder would image that's
> necessary. It's kinda like the Unix way where if you're root, you can
> do something incredibly stupid. I'm sure if a builder is created,
> though, the user will still be able to enter their own parameters for
> tickets. Since there is no builder, that means thought needs to be put
> into creating the queries to get it to show you what you want. Perhaps
> a happy medium for now is a wiki/document on sample queries for
> tickets.
>

Sample queries are important, but modifying samples to fully make use of
additional fields defined by the user still requires modifying SQL
statements.

In my experience, most such query builders provide a means to select and
order the fields and a means for assembly simple conditionals ( "field"
"operator" "value" ) and connect the conditionals with AND or OR. (see
attached screen picture for an actual example)

Would need a way for Fossil to supply the builder with a list of all the
ticket fields and the valid values for each field. The default
"tktsetup_com" illustrates a convention for associating lists of valid
values with fields.. Just need to clearly state the convention. Also need
to extend this convention to specifying ranges and value types.

(I could help create a proof of concept based on the "Edit Ticket" page,
writing TH1 code to supply a browser based builder with the needed
information, but would need help with the builder itself. Ultimately, the
"rptnew" and "rptedit" pages would have to be modified to support the query
builder.)
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to