[wp-meta] [Making WordPress.org] #6508: Make Report 27 dynamic
Making WordPress.org
noreply at wordpress.org
Tue Oct 4 01:59:42 UTC 2022
#6508: Make Report 27 dynamic
-----------------------------+---------------------
Reporter: desrosj | Owner: (none)
Type: feature request | Status: new
Priority: normal | Milestone:
Component: Trac | Resolution:
Keywords: |
-----------------------------+---------------------
Comment (by dd32):
Replying to [comment:2 desrosj]:
> I tried to find a report grouping by component to copy the sequel but
wasn't able to.
Not really.. Trac is poorly documented IMHO.
https://trac.edgewall.org/wiki/1.1/TracReports is the best you'll get.
It's just SQL though, so..
- Add `component as __group__,` to the SQL, save, view the report and
realise it's not sorted by components (but is now visually grouped) -
IMHO: `__...__` fields should be at the start of the `SELECT` for
visibility, so after the `__color__` field
- Adjust the ordering to `ORDER BY component, ...` to ensure it's sorted
appropriately.
I've just made those changes to confirm it works, but I've undone it so
you can try it yourself @desrosj :)
So notably, whatever you return as the `__group__` field is what will be
the grouping shown, every time Trac see's that field change in the results
it outputs a new heading. That means you need the results to be ordered
like `A, A, A, B, C, C` rather than `A, B, C, C, A, A`.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/6508#comment:3>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list