tickets
2 rows where "created" is on date 2008-08-19 and resolution = "wontfix" sorted by resolution
This data as json, CSV (advanced)
Suggested facets: last_pulled_from_trac (date)
id | created | changetime | last_pulled_from_trac | stage | status | component | type | severity | version | resolution ▼ | summary | description | owner | reporter | keywords | easy | has_patch | needs_better_patch | needs_tests | needs_docs | ui_ux |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
8418 | 2008-08-19 15:13:26 | 2008-10-15 03:03:57 | 2022-03-06 03:42:12.811281 | Unreviewed | closed | Generic views | dev | wontfix | archive_year should pass a date year object to template context instead of four digit unicode | The date_based generic view to manage years should pass year as a date object to template context in order to be coherent with other date_based generic views. | nobody | esauro@gmail.com | 0 | 0 | 0 | 0 | 0 | 0 | |||
8420 | 2008-08-19 15:58:25 | 2011-09-28 16:12:17 | 2022-03-06 03:42:13.131119 | Unreviewed | closed | Generic views | dev | wontfix | Inconsistent use of template_name in generic views | Nearly all generic views use the parameter ''template_name'' to provide a custom template for rendering purposes. But, the generic view ''django.views.generic.simple.direct_to_template'' uses the parameter ''template'' instead of ''template_name'' for exactly the same. This is an inconsistency that probably should be fixed before releasing 1.0. | nobody | benjixx | 0 | 0 | 0 | 0 | 0 | 0 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE tickets ( id int primary key, created datetime, changetime datetime, last_pulled_from_trac datetime, stage text, status text, component text, type text, severity text, version text, resolution text, summary text, description text, owner text, reporter text, keywords text, easy boolean, has_patch boolean, needs_better_patch boolean, needs_tests boolean, needs_docs boolean, ui_ux boolean );