Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: Current Version
-
Fix Version/s: TAG 2016/17 Sprint 2
-
Component/s: OIOIOI
-
Labels:None
Description
And these choices actually depend on the set of configured apps. We should not serialize the choices and create database fields which do not limit the content of these fields.
I suppose we need a custom EnumField.
I suppose we need a custom EnumField.
Activity
Field | Original Value | New Value |
---|---|---|
Fix Version/s | Next Sprint [ 12002 ] |
Assignee | Szymon Acedański [ accek ] |
Assignee | Szymon Acedański [ accek ] | Szymon Pajzert [ szymonpajzert ] |
Fix Version/s | TAG 2016/17 Sprint 2 [ 12502 ] | |
Fix Version/s | Next Sprint [ 12002 ] |
Status | New [ 10000 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
Transition | Time In Source Status | Execution Times | Last Executer | Last Execution Date | |||||
---|---|---|---|---|---|---|---|---|---|
|
763d 17h 59m | 1 | Szymon Pajzert | 2017-03-14 11:28 | |||||
|
742d 5h 11m | 1 | Szymon Acedański | 2019-03-26 16:39 |
https://gerrit.sio2project.mimuw.edu.pl/2672
SIO-1600Django 1.7 migrations serialize choices for EnumFieldsChange-Id: I363b0d323236f24ca10d8e778a614e6a3991c1d0