-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
4.16.0
-
1
-
Severity 3 - Minor
-
Issue Summary
When accessing an Insight object loaded from a custom field via the Java api, the method getObjectAttributeBeans() does not return Attribute beans of the type text area.
Steps to Reproduce
- Create a new custom field of any insight type.
- Fill it with an object that has a text area attribute.
- Then get the value as a (mutable) objectbean with Insight JAVA API:
ex:((issue.getCustomFieldValue(customFieldManager.getCustomFieldObject(10145)) as List<*>).firstOrNull() as MutableObjectBean)
Expected Results
This objectBean should include all attributes.
Actual Results
This objectBean will not include all attributes.
Workaround
As clarified by Insight devs this happen because textarea attribute is not set on indexed when newly created.
To workaround the issue edit the settings for the attribute textarea and flag it as indexed:
- links to
[JSDSERVER-7376] Insight JAVA API method getObjectAttributeBeans() does not return Attribute beans of the type textarea when loading the object from custom field
Labels | New: ril |
Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 955274 ] |
Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
Support reference count | New: 1 |
Summary | Original: Insight JAVA API method getObjectAttributeBeans() does not return Attribute beans of the type text area when loading the object from custom field | New: Insight JAVA API method getObjectAttributeBeans() does not return Attribute beans of the type textarea when loading the object from custom field |
Hello,
i have an better worakaround for the Programmer's because how did u wil evaluate that all Textarea fields are set the index checkbox?
First the story for my WA i'm an Programmer and the first thing that i read is not the User doc its the java doc wich i read first and playing with it. To get the Attr. i was using for the first time the same way as the reporter and get the same Bug. (get field value and the Attributes of it) I was wondering why this happens and the first in my mind was ok there is an Manager Class that could be used to specialy load the object by an Id and tada the second workaround was born. If u load the Object bean by the manager class the bug not happens.
Cheers,
Heiko