tickets

27 rows where "created" is on date 2008-08-15 sorted by last_pulled_from_trac

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: changetime, stage, resolution, owner, needs_better_patch, changetime (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
8328 2008-08-15 00:34:12 2011-09-28 16:12:17 2022-03-06 03:41:57.740539 Accepted closed Documentation     dev fixed [8240] contained undocumented backwards incompatible change Changeset [8240] added code to override the default widget for certain field types in the admin. This is a backwards incompatible change and should be listed on the doc page for such changes. (I was using a custom field which subclassed IntegerField and specified its own custom widget, which I would guess isn't such a rare use case, and this change broke my code. My workaround was just to manually delete 'widget' from kwargs in the constructor for my field class, but the lack of documentation meant it took a while to track down the problem.) nobody mmulley   0 0 0 0 0 0
8329 2008-08-15 01:39:48 2011-12-22 22:17:13 2022-03-06 03:41:57.926726 Accepted closed Core (Management commands) New feature Normal dev fixed django shouldn't delete the startproject command but put a warning in it's place   IanHolsman   0 1 1 1 0 0
8330 2008-08-15 02:40:10 2008-08-15 02:45:29 2022-03-06 03:41:58.059140 Unreviewed closed contrib.admin     dev duplicate Cannot add new filterspecs without modifining filterspecs.py Adding your own filter specs works easily by simply using this code within an applications admin.py {{{ #!python from django.contrib.admin.filterspecs import FilterSpec class MyFilterSpec(FilterSpec): ... FilterSpec.register(...) }}} However, since the last default FilterSpec is always evaluated as True, and new FilterSpec's never get tested. It doesn't seem right to require a library file be modified in order to add a a feature to an application (for example, django-tagging which is what I was messing with when I found this.) Since I don't know exactly what channels I should be going through to submit this as a patch, I'll just put the solution I found here. It's easy to fix if you add the following the FilterSpec. {{{ #!python class FilterSpec(object): filter_specs = [] default = None #added ... def create(cls, f, request, params, model, model_admin): for test, factory in cls.filter_specs: if test(f): return factory(f, request, params, model, model_admin) ### added after this point if callable(default): return default(f, request, params, model, model_admin) create = classmethod(create) # new method def set_default(cls, factory): if callable(factory): cls.default = factory set_default = classmethod(set_default) }}} Then, just replace the last line (which registers AllValuesFilterSpec) with: {{{ #!python FilterSpec.set_default(AllValuesFilterSpec) }}} nobody elwaywitvac <elwaywitvac@gmail.com> Filters 0 1 0 0 0 0
8331 2008-08-15 03:05:46 2008-08-15 07:41:36 2022-03-06 03:41:58.224901 Unreviewed closed Core (Management commands)     dev fixed manage.py sqlclear and friends crash, for unknown reasons When I run manage.py sqlclear, it often crashes with the following traceback: {{{ $ ./manage.py sqlclear tests Traceback (most recent call last): File "./manage.py", line 11, in <module> execute_manager(settings) File "/Library/Python/2.5/site-packages/django/core/management/__init__.py", line 334, in execute_manager utility.execute() File "/Library/Python/2.5/site-packages/django/core/management/__init__.py", line 295, in execute self.fetch_command(subcommand).run_from_argv(self.argv) File "/Library/Python/2.5/site-packages/django/core/management/base.py", line 77, in run_from_argv self.execute(*args, **options.__dict__) File "/Library/Python/2.5/site-packages/django/core/management/base.py", line 96, in execute output = self.handle(*args, **options) File "/Library/Python/2.5/site-packages/django/core/management/base.py", line 146, in handle app_output = self.handle_app(app, **options) File "/Library/Python/2.5/site-packages/django/core/management/commands/sqlclear.py", line 10, in handle_app return u'\n'.join(sql_delete(app, self.style)).encode('utf-8') File "/Library/Python/2.5/site-packages/django/core/management/sql.py", line 98, in sql_delete output.extend(connection.creation.sql_destroy_model(model, references_to_delete, style)) File "/Library/Python/2.5/site-packages/django/db/backends/creation.py", line 263, in sql_destroy_model output.extend(self.sql_remove_table_constraints(model, references_to_delete, style)) TypeError: sql_remove_table_constraints() takes exactly 3 arguments (4 given) }}} As far as I can tell, though, sql_remove_table_constraints() does actually want four arguments (including self). An example for which this happens is a simple project, with only the one app installed, whose models.py looks like {{{ from django.db import models class Watcher(models.Model): user = models.ForeignKey('User') class User(models.Model): pass }}} If you switch the order of the definitions, however, i… nobody d00gs   0 0 0 0 0 0
8332 2008-08-15 04:26:05 2008-08-15 15:22:32 2022-03-06 03:41:58.366254 Unreviewed closed Uncategorized     dev duplicate delete generates faulty sql for subclasses of non-abstract parents Stack trace is attached. Student is a subclass of Person. Person has a ForeignKey field pointing to Address. delete() calls the sql '''UPDATE "tables_student" SET "address_id" = NULL WHERE "person_ptr_id" IN''' Since address_id is a field of tables_person, this throws an exception. Assuming CollectedObjects() is doing the right thing, the (a?) correct behavior would be to pass over address_id in line 836 of db/models/query.py (see below) when it shows up as a field of Student. After deleting the Student record, delete_objects will reach the related Person record, which has the real address_id field, set that to Null, and then delete the Address record. The code I'm proposing changing: {{{ 831 del_query.delete_batch_related(pk_list) 832 833 update_query = sql.UpdateQuery(cls, connection) 834 for field in cls._meta.fields: 835 if field.rel and field.null and field.rel.to in seen_objs: 836 -> update_query.clear_related(field, pk_list) }}} I'm interested in testing the boundaries of this bug and writing a patch. I'm hoping someone can tell me if there's an easy way to test (line 835) whether field is local to cls or inherited from a parent. bergey bergey   0 0 0 1 0 0
8333 2008-08-15 04:31:22 2008-08-15 07:20:51 2022-03-06 03:41:58.514041 Unreviewed closed File uploads/storage     dev duplicate FileField upload of large files looping and failing Tripped on this while trying to update photologue, testing a large zip file. Then tried some of my own code and found that wasn't working with large files either. Uploads work fine for 1 meg files Tried 20meg files and it goes into an upload loop during the save. Uploads the file, lets say "BIG_FILE", then "BIG_FILE_" and so on "BIG_FILE_..._" until it fails on a filename of 215+ characters. All the files that are uploaded are complete and are not corrupt. I'm running on Windows with Apache and mod_python. MODEL {{{ class UploadedDocument( models.Model ): file = models.FileField( upload_to = 'uploads/documents/') description = models.CharField( max_length=255, blank=True, help_text='Description of document.') uploaded_by = models.ForeignKey( User ) }}} FORM {{{ class DocumentField(forms.FileField): def __init__(self, *args, **kwargs): super(DocumentField, self).__init__(*args, **kwargs) self.label = 'New File' self.help_text = 'Select a doc, rtf, or pdf document' def clean(self, data, UNKNOWN_FIELD): f = super(DocumentField, self).clean(data) if data in (None, ''): " Required=False and no data... " return None file_types = ('application/msword', 'application/rtf', 'application/pdf') file_exts = ('.doc', '.rtf', '.pdf') if (not splitext(f.name)[1].lower() in file_exts) and (not data['content-type'] in file_types): raise forms.ValidationError('Document types accepted: %s' % ' '.join(file_exts)) return f class UploadedDocumentForm(ModelForm): file = DocumentField(required=True, widget=forms.FileInput(attrs={'size':'80'})) description = forms.CharField(required=True, help_text=UploadedDocument._meta.get_field('description').help_text, widget=forms.Textarea(attrs={'style':'width:98%; height:3em;' })) class Meta: … nobody tapautler filefield upload looping 0 0 0 0 0 0
8334 2008-08-15 06:38:37 2011-04-26 22:33:16 2022-03-06 03:41:58.666114 Accepted closed Database layer (models, ORM) New feature Normal dev duplicate Allow add/create on m2m intermediate tables if all the non-FK fields have defaults or are NULLable Add/create is currently disabled on m2m relations that use an intermediate table. This is due to the fact that values to populate the intermediate table cannot be provided using the add/create calls. However, what if the intermediate model has reasonable default values, so one can assign model A to B without extra info? In my case, I just want to syncronize 2 databases, and I would like to mark relationships, that are already synced. So, in my case, the intermediate table contains a boolean, which defaults to false, and will become true, when the data is synced. In this case adding relations without explicitly creating the intermediate table would be great. (based on [http://groups.google.com/group/django-users/browse_thread/thread/a40f1005760f80b5 this thread in the ML]) nobody pihentagy manytomany through default add create 0 0 0 0 0 0
8335 2008-08-15 06:50:39 2011-09-28 16:12:17 2022-03-06 03:41:58.830786 Unreviewed closed Uncategorized     dev invalid django.get_version() does not return SVN revision I#m using current SVN co. Revision 8363. Since 1.0 beta2 SVN revision is not returned by django.get_version(), instead there's just 'SVN-unknown'. nobody marcusti   0 0 0 0 0 0
8336 2008-08-15 07:07:48 2009-07-17 16:28:38 2022-03-06 03:41:58.967262 Design decision needed closed django-admin.py runserver     dev wontfix runserver option for disabling admin static files serving Okay, it's handy not to worry about admin media files static serving, when running simple dev server.. But if you want to do something special with admin media files, like not touching the original ones in `django.contrib.admin` and add some of your own, like we do with very simple static serving view (serve from one dir and fallback to another), you must set `ADMIN_MEDIA_PREFIX = 'http://localhost:8000'`, which is not very portable solution, or symlink files from various dirs and let runserver serve admin static files from there. If people have in their urls.py something for static media serving when `DEBUG == True` - why not to have there the same for admin? I'll attach patch that adds an option for runserver management command which gives you the chance just to disable builtin magical serving. nobody jakub_vysoky admin media runserver 0 1 0 0 0 0
8337 2008-08-15 08:32:33 2011-09-28 16:12:17 2022-03-06 03:41:59.104779 Ready for checkin closed Documentation     dev fixed Minor typo in model api doc Just a small typo in [8365] ;) nobody julien   0 1 0 0 0 0
8338 2008-08-15 08:34:15 2011-09-28 16:12:17 2022-03-06 03:41:59.251121 Unreviewed closed Template system     dev worksforme Admin panel generating HTML table without <input> fields if variable contains "_A" string = Main information = Admin panel generating HTML table to enter data. [[BR]] But if object contains '_' char and after that is letter 'A' [[BR]] ( for example: 'Foo_Address' ) [[BR]] adv_forms don't creates fields ( INPUT field in HTML) [[BR]] == Django version == Django ver: SVN-checkout: rev.8365 [[BR]] {{{ # -*- coding: utf-8 -*- from django.db import models from django.contrib import admin from django.utils.translation import ugettext as _ class Foo(models.Model): foo = models.CharField(verbose_name=_('FOO'), max_length=11) class Foo_Address(models.Model): foo = models.ForeignKey(Foo) bar = models.CharField(max_length=11) class Foo_Faddress(models.Model): foo = models.ForeignKey(Foo) bar = models.CharField(max_length=11) class Foo_Address_Inline(admin.TabularInline): model = Foo_Address extra = 1 class Foo_Faddress_Inline(admin.TabularInline): model = Foo_Faddress extra = 1 class Foo_Admin(admin.ModelAdmin): inlines = [Foo_Address_Inline, Foo_Faddress_Inline] admin.site.register(Foo, Foo_Admin) }}} [http://img367.imageshack.us/img367/3876/zrzutekranuba1.png Screenshot] nobody bartosak no input fields html admin panel 0 0 0 0 0 0
8339 2008-08-15 09:33:37 2008-08-15 14:24:48 2022-03-06 03:41:59.420076 Unreviewed closed contrib.admin     dev invalid Problem with behaviour of ManyToManyField I have a problem using the ManyToManyFied with an already existing database. I have two tables called AVAILABILITY and TESTDEF that are linked together according to a n-n relationship. I have defined them as following in my models.py file (with the help of inspectdb). The names of the columns in the tables are the same as the python names. {{{ class Testdef(models.Model): testid = models.DecimalField(max_digits=38, decimal_places=0, primary_key=True) testname = models.CharField(max_length=100) testtitle = models.CharField(max_length=255, blank=True) testabbr = models.CharField(max_length=50, blank=True) def __unicode__(self): return self.testname+' ('+self.testabbr+')' class Meta: db_table = u'TESTDEF' class Availability(models.Model): availabilityid = models.AutoField("Id", primary_key=True, null=False) availabilityname = models.CharField("Name", max_length=255) bdiiflag = models.CharField("BDii", max_length=1, choices=(('Y', "Yes"),('N', "No"),)) void = models.ForeignKey(Vo, db_column='void') tests = models.ManyToManyField(Testdef, db_table='AVAILABILITYTESTCRITICALITY', related_name='availabilityid') def __unicode__(self): return self.availabilityname class Meta: db_table = u'AVAILABILITY' verbose_name_plural = u'Availabilities' }}} The linking table is called AVAILABILITYTESTCRITICALITY, and has the following fields: AVAILABILITYID, TESTID I use this environment: {{{ Environment: Request Method: GET Request URL: http://localhost:8000/admin/avl/availability/6/ Django Version: 1.0-alpha_2-SVN-unknown Python Version: 2.3.4 Installed Applications: ['django.contrib.auth', 'django.contrib.contenttypes', 'django.contrib.sessions', 'django.contrib.sites', 'django.contrib.admin', 'django.contrib.databrowse', 'mysite.avl'] Installed Middleware: ('django.middleware.common.CommonMiddleware', 'django.contrib.sessions.middleware.SessionMiddleware', 'django.contrib.auth.midd… nobody guneeyoufix   0 0 0 0 0 0
8340 2008-08-15 09:36:25 2011-09-28 16:12:17 2022-03-06 03:41:59.581553 Accepted closed Uncategorized     dev fixed MySQL case sensitivity and utf8_bin / 2710 As noted in the documentation, I tried to change the collation within my Django-database. So I dumped the database and changed "utf8_german_ci" to "utf8_bin". After restoring the data and trying to open one page, I'll get the following error (I'm using the latest svn-version 8366): {{{ [Fri Aug 15 08:52:23 2008] [error] [client 192.168.0.222] mod_python (pid=2259, interpreter='dms', phase='PythonHandler?', handler='django.core.handlers.modpython'): Application error [Fri Aug 15 08:52:23 2008] [error] [client 192.168.0.222] ServerName?: 'www.dms.bildung.hessen.de' [Fri Aug 15 08:52:23 2008] [error] [client 192.168.0.222] DocumentRoot?: '/srv/www/htdocs' [Fri Aug 15 08:52:23 2008] [error] [client 192.168.0.222] URI: '/news/index.html' [Fri Aug 15 08:52:23 2008] [error] [client 192.168.0.222] Location: None [Fri Aug 15 08:52:23 2008] [error] [client 192.168.0.222] Directory: None [Fri Aug 15 08:52:23 2008] [error] [client 192.168.0.222] Filename: '/srv/www/htdocs/news' [Fri Aug 15 08:52:23 2008] [error] [client 192.168.0.222] PathInfo?: '/index.html' [Fri Aug 15 08:52:23 2008] [error] [client 192.168.0.222] Traceback (most recent call last): [Fri Aug 15 08:52:23 2008] [error] [client 192.168.0.222] File "/usr/lib64/python2.5/site-packages/mod_python/importer.py", line 1537, in HandlerDispatch?\n default=default_handler, arg=req, silent=hlist.silent) [Fri Aug 15 08:52:23 2008] [error] [client 192.168.0.222] File "/usr/lib64/python2.5/site-packages/mod_python/importer.py", line 1229, in _process_target\n result = _execute_target(config, req, object, arg) [Fri Aug 15 08:52:23 2008] [error] [client 192.168.0.222] File "/usr/lib64/python2.5/site-packages/mod_python/importer.py", line 1128, in _execute_target\n result = object(arg) [Fri Aug 15 08:52:23 2008] [error] [client 192.168.0.222] File "/usr/local/lib64/python2.5/site-packages/django/core/handlers/modpython.py", line 210, in handler\n return ModPythonHandler?()(req) [Fri Aug 15 08:52:23 2008] [error] [client 192.168.0.222] File "/u… mtredinnick hrauch   0 0 0 0 0 0
8341 2008-08-15 09:40:21 2012-06-26 11:49:37 2022-03-06 03:41:59.764814 Accepted closed contrib.admin Uncategorized Normal dev fixed InlineModelAdmin is missing `can_delete` and `can_order` `InlineModelAdmin` causes one to override whole function (`get_formset`) because it is missing, `can_delete` and `can_order` from the `inlineformset_factory` call. P.S. Not related to this patch: Also there should be ability to give different form for `change_view` and `add_view` without such a big overriding. nobody ciantic@mbnet.fi   0 1 0 0 0 0
8342 2008-08-15 10:01:49 2013-08-04 12:08:17 2022-03-06 03:41:59.925849 Accepted closed contrib.admin     dev fixed The admin wrongly assumes you can't login with your email On one of my sites, I have a custom authentication backend which allows you to login with your email, and just your email (the `username` attribute is basically ignored in the process). It works fine, you can login both on the front-end site and on the admin site with your email. However, if you mistype the email address or try to login with an email that doesn't exist, in the admin, then you get the message "Usernames cannot contain the '@' character.". I don't know what's the best approach to fix this. I report now and will try to think of a patch. This is something that I think is important to fix before 1.0, as that error message is quite misleading. nobody julien   0 1 1 0 0 0
8343 2008-08-15 10:56:19 2008-08-15 15:14:21 2022-03-06 03:42:00.095353 Unreviewed closed Uncategorized     dev worksforme Using umlauts with blocktrans results in TemplateSyntaxError /project/app/locale/de/django.po: msgid "foomsg %(val)s %(val)s" msgstr "Föö bar %(val)s foo %(val2)s% /project/app/templates/foo.html: {% blocktrans with c.foo as val and c.bar as val2 %}foomsg {{ val }}{{ val2 }}{% endblocktrans %} Result: Page is not rendered but a TemplateSyntaxError is thrown: Caught an exception while rendering: 'ascii' codec can't decode byte 0xc3 in position 3: ordinal not in range(128) nobody oliverw localization 0 0 0 0 0 0
8344 2008-08-15 12:11:35 2011-09-28 16:12:17 2022-03-06 03:42:00.247435 Accepted closed contrib.auth     dev fixed contrib.auth.models.User.get_profile() throws AttributeError not SiteProfileNotAvailable On line [http://code.djangoproject.com/browser/django/trunk/django/contrib/auth/models.py?rev=8366#L289 line 289] it checks if {{{settings.AUTH_PROFILE_MODULE}}} is set. This throws an {{{AttributeError}}} instead of the {{{SiteProfileNotAvailable}}} exception, if the setting is not given. The attached patch fixes the issue. jezdez jezdez   0 1 0 0 0 0
8345 2008-08-15 13:55:16 2011-09-28 16:12:17 2022-03-06 03:42:00.520300 Accepted closed Translations     dev fixed Dutch translations, getting ready for 1.0 string-freeze I updated the Dutch translations after beta-1 for Django 1.0 got realeased. It's 100% complete. I've attached the complete .po file since a diff would also be rather big. The djangojs.po did not change. I'm planning to keep this ticket up-to-date until the strings are completely frozen. nobody Rudolph   0 1 0 0 0 0
8346 2008-08-15 15:52:23 2011-09-28 16:12:17 2022-03-06 03:42:00.663341 Accepted closed Forms     dev duplicate overriding widget in ModelChoiceField doesn't work as expected Using below custom ModelChoiceField will not use RadioSelect widget as expected. {{{ class MyModelChoiceField(forms.ModelChoiceField): widget = forms.RadioSelect }}} You can work around that issue by overriding __init__ like so: {{{ class MyModelChoiceField(forms.ModelChoiceField): def __init__(self, *args, **kwargs): return super(MyModelChoiceField, self).__init__(widget=forms.RadioSelect, *args, **kwargs) }}} I guess this is a bug either with ModelChoiceField or with the documentation. nobody derelm     0 0 0 0  
8347 2008-08-15 16:05:44 2011-09-28 16:12:17 2022-03-06 03:42:00.811914 Accepted closed Database layer (models, ORM)     dev fixed missing fields/definitions in sqlite3 introspection module The floatfield is missing in sqlite3 introspection module, 'real' fields in sqlite3 are suppose to use FloatField in Django ORM. Attached is a very simple patch to add it to the base_data_types_reverse list. nobody trbs sqlite, missing, fields, introspection 0 1 0 0 0 0
8348 2008-08-15 16:31:47 2014-06-06 20:33:08 2022-03-06 03:42:00.941851 Accepted closed Core (Management commands) New feature Normal dev fixed Feature request: -n/--no-act option to syncdb I'm about to run {{{syncdb}}} on a project I help maintain, but I don't know what it's going to add to the database because I may not have been the last one to touch it. It would be helpful to have a {{{-n/--no-act}}} option that would report what it would do, but not actually do it. anonymous kcarnold syncdb 0 1 1 0 0 0
8349 2008-08-15 16:57:26 2008-08-25 15:57:49 2022-03-06 03:42:01.092511 Unreviewed closed Core (Management commands)     dev wontfix syncdb doesn't make all the necessary changes with the Oracle backend I'm using the Oracle backend, with an already existing database. I had to make changes to the output of the inspectdb command so that my models.py and the actual database matched. However, no matter how often I issue the syncdb command, some sequences and triggers won't be created (basically all of the triggers that are directly related to my application). I have attached the output of the sqlall command for the concerned app. nobody guneeyoufix   0 0 0 0 0 0
8350 2008-08-15 17:25:23 2011-09-28 16:12:17 2022-03-06 03:42:01.252629 Ready for checkin closed Documentation     dev duplicate Part 2 of Tutorial references get_admin_app_list as app_list In Tutorial 2, in the section titled Customize the admin index page, the tutorial tells you to copy django/contrib/admin/templates/admin/index.html and informs you that the tag {% get_admin_app_list as app_list %} gets the list of apps. get_admin_app_list appears to no longer be used. swillmon Jacob Fenwick <jfenwick@mitre.org>   0 1 0 0 0 0
8351 2008-08-15 19:06:06 2008-08-16 15:54:37 2022-03-06 03:42:01.396868 Unreviewed closed contrib.sessions     dev fixed load() method of the cache SessionStore backend returns None As of [8440], the `load()` method of the cache `SessionStore` backend returns None instead of `{}` if the `session_data` is None. mtredinnick trevor   0 1 0 0 0 0
8352 2008-08-15 20:15:23 2008-08-15 21:14:22 2022-03-06 03:42:01.554018 Unreviewed closed Documentation     dev fixed Misspelling near the end of contenttypes doc In the last paragraph of http://www.djangoproject.com/documentation/contenttypes/ (the paragraph titled: Generic relations in forms and admin), In the first sentence the module is described as: django.contrib.contenttypes.genric it should be: django.contrib.contenttypes.generic nobody cjs   0 0 0 0 0 0
8353 2008-08-15 21:33:35 2011-09-28 16:12:17 2022-03-06 03:42:01.720543 Accepted closed contrib.admin     dev fixed TemplateSyntaxError when adding user in admin When trying to add a user in admin you get a TemplateSyntaxError (url: <server>/admin/auth/user/add/). It's in the file: django/contrib/admin/templates/admin/change_form.html on line 61 {{{ {% prepopulated_fields_js %} }}} When outcommented, the error disappear. brosner marzim   0 0 0 0 0 0
8354 2008-08-15 21:48:01 2011-09-28 16:12:17 2022-03-06 03:42:01.865581 Accepted closed Database layer (models, ORM)     dev fixed MySQL rejects datetimes with unusual unicode() representations The database adapters assume that {{{unicode(datetime.datetime)}}} will return a string that can be passed to the database. Unfortunately, this assumption is false. Datetime objects with timezones will be formatted as a string that can't be read by MySQL: {{{ >>> test_date datetime.datetime(2008, 8, 15, 21, 31, 8, tzinfo=<UTC>) >>> print unicode(test_date) 2008-08-15 21:31:08+00:00 }}} I've patched the MySQL database adapter to use {{{datetime.strftime()}}} instead of {{{unicode}}} (patch attached). This sort of patch should probably be adapted to other database adapters, so they have more consistent datetime formatting. nobody jmillikin 1.0-blocker 0 1 1 1 0 0

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

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
    );