-
Bug
-
Resolution: Fixed
-
Low
-
5.10.1
-
2
-
Severity 3 - Minor
-
11
-
Issue Summary
If Status attributes in the table AO_8542F1_IFJ_OBJ_TYPE_ATTR Have any DEFAULT_TYPE_ID that isn't -1 then the status field stops functioning correctly.
Origin of why the value changed to 0 or another value is unknown.
This is reproducible on Data Center: (yes)
Steps to Reproduce
- Startup JSM DC
- Create a default templated project with ITSM Assets
- Go into the SQL Pad and Modify any of the rows in AO_8542F1_IFJ_OBJ_TYPE_ATTR where TYPE = 7 to have a value in DEFAULT_TYPE_ID that is not -1
- Restart Jira
- Try and update any object that has a status field and the status may not sometimes remain
Expected Results
Software should report an error if the attribute isn't correctly formulated to function, or optimally self correct
Actual Results
No errors and the attribute sometimes does not persist.
Workaround
Check for invalid entries:
select * from "AO_8542F1_IFJ_OBJ_ATTR" afioa join "AO_8542F1_IFJ_OBJ_TYPE_ATTR" afiota on afiota."ID" = afioa."OBJECT_TYPE_ATTRIBUTE_ID" where afiota."TYPE" = '7' and afiota."DEFAULT_TYPE_ID" != '-1';
Correct any invalid entries with the following query:
update "AO_8542F1_IFJ_OBJ_TYPE_ATTR" as afiota set "DEFAULT_TYPE_ID" = '-1' where afiota."TYPE" = '7' and afiota."DEFAULT_TYPE_ID" != '-1'
- duplicates
-
JSDSERVER-11246 Creating an ObjectType attribute of Type "Default" without "Type Value" makes all the attributes of the ObjectType unavailable
-
- Gathering Impact
-
- mentioned in
-
Page Failed to load