django_tickets: tickets: 2 rows where "created" is on date 2005-07-13 and stage = "Someday/Maybe" sorted by resolution

2 rows where "created" is on date 2005-07-13 and stage = "Someday/Maybe" sorted by resolution

descending

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
29	2005-07-13 19:43:02	2015-11-07 09:54:25	2022-03-06 03:19:31.418555	Someday/Maybe	closed	contrib.admin	Bug	Normal	dev	wontfix	Fix usability issue with limit_choices_to and "Add another" in admin	{{{ django34: We have the ability to put a customized limit/filter on which related objects get displayed in select boxes. For instance, the "photographer" field on the "Add photo" form only displays the "Staff members" that have shoots_photos=True. django34: This results in some usability problems, though, because if a producer doesn't see a person's name in the list, he might click "Add another..." instead of checking to make sure the person isn't in "Staff members" and doesn't have "shoots_photos" checked. django34: Does this make sense? wilson: kind of wilson: what page would that case appear on django34: Here's an example... django34: The "Photographer" select box includes only the staff members that have shoots_photos=True. django34: So if a producer doesn't see a photographer in there, he might click "Add another...", which would create an entirely new staff member. But it might be the case that the staff member DOES exist, just doesn't have shoots_photos=True checked. wilson: if the staff member did exist, would it let them add them again? django34: Yes, as long as the slug was different. django34: The only way I can think of to fix this would be to have some sort of "Showing only photographers [Show all staff members]" link. Or to eliminate the filtering altogether. wilson: i was going to suggest a "show all staff" link wilson: yes, that is my suggestion wilson: "show all staff" link next to the select wilson: then "show photographers only" when the filter is off django34: All right. }}}	nobody	adrian		0	0	0	0	0	1
27	2005-07-13 19:40:29	2014-06-08 07:20:52	2022-03-06 03:19:31.121463	Someday/Maybe	closed	Forms	New feature	Normal		worksforme	Single form field for multiple database fields	Some admin interfaces would benefit from being able to have multiple fields' worth of data entered in a single field. For example, a field for a sports stat could be entered into a single field as "XX-YY-ZZ", whereas the three values are actually three separate fields in the DB. Relevant conversation: {{{ <jacobkm> Well, I'm using those aggregate fields for stats where you type something like "3-17" and it gets split into multiple fields. I see there's a CommaSeperatedIntegerField in formfields which would work for this, but there needs to be a way in the datadescriptions to say "this group of fields should be presented as a single field" <django34> The DD will have to provide a format string of some sort <jacobkm> Easy enough <jacobkm> are you thinking of a % format string or a regex? <django34> Not sure... <django34> Probably just % <django34> fields_together = '%(last_name)s, %(first_name)s' }}}	nobody	adrian		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
    );