-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
4
-
In Jira Service Management 5.13, we updated the editor in Assets for textarea attributes.
Since then, the following tag is added to Object History
<div class="created-with-ak-editor content-wrapper">
Furthermore. when a textArea attribute is updated, all other textArea attributes are being resaved, even though only one textArea attribute was updated.
This creates an excessive "noise" being recorded. Specifically, the history now reflects changes even when no modifications are made to an attribute. This could lead to misunderstandings and defeats the purpose of having a clear and accurate history
Recommendation
- Not showing the wrapper element in the object history value; and
- If the only change to the content is the wrapper element, not to create an object history event
- links to
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDSERVER-15524] Improve the way the Assets Object history works after 5.13
| UIS | New: 1 |
| Support reference count | Original: 3 | New: 4 |
| Support reference count | Original: 2 | New: 3 |
| Support reference count | New: 2 |
| Assignee | Original: Shreekesh Mohan [ 072fabfd41a3 ] |
| Assignee | New: Shreekesh Mohan [ 072fabfd41a3 ] |
| Labels | New: ril |
| Remote Link | New: This issue links to "Internal ticket (Web Link)" [ 978827 ] |
| Description |
Original:
In [Jira Service Management 5.13|https://confluence.atlassian.com/servicemanagement/jira-service-management-5-13-x-release-notes-1306297689.html#JiraServiceManagement5.13.xreleasenotes-neweditor], we updated the editor in Assets for textarea attributes.
Since then, the following tag is added to Object History {noformat} <div class="created-with-ak-editor content-wrapper"> {noformat} Furthermore. when a textArea attribute is updated, all other textArea attributes are being resaved, even thought only one textArea attribute was updated. This creates an excessive "noise" being recorded. Specifically, the history now reflects changes even when no modifications are made to an attribute. This could lead to misunderstandings and defeats the purpose of having a clear and accurate history h3. Recommendation # Not showing the wrapper element in the object history value; and # If the only change to the content is the wrapper element, not to create an object history event |
New:
In [Jira Service Management 5.13|https://confluence.atlassian.com/servicemanagement/jira-service-management-5-13-x-release-notes-1306297689.html#JiraServiceManagement5.13.xreleasenotes-neweditor], we updated the editor in Assets for textarea attributes.
Since then, the following tag is added to Object History {noformat} <div class="created-with-ak-editor content-wrapper"> {noformat} Furthermore. when a textArea attribute is updated, all other textArea attributes are being resaved, even though only one textArea attribute was updated. This creates an excessive "noise" being recorded. Specifically, the history now reflects changes even when no modifications are made to an attribute. This could lead to misunderstandings and defeats the purpose of having a clear and accurate history h3. Recommendation # Not showing the wrapper element in the object history value; and # If the only change to the content is the wrapper element, not to create an object history event |