-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
4.4, 4.4.3
-
None
-
4.04
-
Steps to reproduce
- Create a select list customfield on a Jira 4.2 instance
- Set the context to some selected issue types and create some issues with these customfield
- Edit the customfield context and disable it for one of the earlier issue types.
- upgrade to 4.4.x
After upgrading JIRA will resort to inconsistent data in the database as values in stringvalue column in the customfieldvalue will be storing the strin value rather than the id of the value derived from the customfieldoption table. This will result in in correct report for users genrating report via the database. Updating the database can be quite frustrating especially if the number of customfiel;ds and options involve is very big.
- mentioned in
-
Page Loading...