tickets
2 rows where "created" is on date 2008-08-28 and type = "New feature" sorted by stage
This data as json, CSV (advanced)
| 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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 8649 | 2008-08-28 16:10:00 | 2013-03-31 08:36:02 | 2022-03-06 03:42:48.597791 | Accepted | closed | Documentation | New feature | Normal | dev | fixed | Document caveats about dynamically adjusting formsets. | See #8171, and especially [http://code.djangoproject.com/ticket/8171#comment:6 the final comment]. | brosner | jacob | 0 | 0 | 0 | 0 | 0 | 0 | |
| 8647 | 2008-08-28 15:57:25 | 2011-09-12 18:59:09 | 2022-03-06 03:42:48.279234 | Design decision needed | closed | contrib.auth | New feature | Normal | dev | duplicate | Add support for user password encryption algorithm selection | User class in django/contrib/auth/models supports crypt algorithm in decoding password but not in the set_password method (see line 175). User password encryption algorithm should have a default but also but also configurable in project settings. Project settings SECRET_KEY should be used in the encryption since all the data needed for brute force cracking are available in a db dump | sammyrulez | password encryption | 0 | 1 | 0 | 1 | 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
);