• Type: Bug
• Resolution: Unresolved
• Priority: Low
• Fix Version/s: None
• Affects Version/s: 5.2.0, 5.4.0, 5.5.0, 5.6.0
• Component/s: Assets - Core experiences, Jira Service Management
• Labels:

  • ril

1. Screen Recording 2023-03-21 at 2.29.27 PM.mov

   54.84 MB

   21/Mar/2023 9:18 AM

[JSDSERVER-12493] Editing the avatar in Assets Object View throws unique attribute error

Marc Dacanay made changes - 14/Oct/2024 11:27 PM

Labels

New: ril

Marc Dacanay made changes - 14/Oct/2024 11:27 PM

Remote Link

New: This issue links to "Internal ticket (Web Link)" [ 955750 ]

SET Analytics Bot made changes - 17/Jan/2024 4:03 AM

Support reference count

Original: 2

New: 3

SET Analytics Bot made changes - 30/Jun/2023 4:03 AM

Support reference count

Original: 1

New: 2

SET Analytics Bot made changes - 22/Mar/2023 4:03 AM

Support reference count

New: 1

Mingyi Yang made changes - 21/Mar/2023 10:36 PM

Status

Original: Needs Triage [ 10030 ]

New: Gathering Impact [ 12072 ]

Sireesha made changes - 21/Mar/2023 9:38 AM

Description

Original: h3. Issue Summary Editing the avatar in Assets Object View throws a unique attribute error. Editing the avatar from the object list view works without any issues. This is reproducible on Data Center: yes h3. Steps to Reproduce  # Create object type where two attributes have the constraint "unique".  # Go to the asset view screen  # Hit the edit button  # Add an avatar, and update.  # Hit the edit button again  # Remove the avatar  # Hit Update h3. Expected Results Avatar was removed and the asset was saved. h3. Actual Results The asset is not saved and both unique attributes throw the message "the attribute... has to be unique". h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available

New: h3. Issue Summary Editing the avatar in Assets Object View throws a unique attribute error. Editing the avatar from the object list view works without any issues. This is reproducible on Data Center: yes h3. Steps to Reproduce  # Create object type where two attributes have the constraint "unique".  # Go to the asset view screen  # Hit the edit button  # Add an avatar, and update.  # Hit the edit button again  # Remove the avatar  # Hit Update h3. Expected Results Avatar was removed and the asset was saved. h3. Actual Results The asset is not saved and both unique attributes throw the message "the attribute... has to be unique". h3. Workaround Please use the '{*}Edit{*}' option from the Object list view to update the avatar.

Sireesha made changes - 21/Mar/2023 9:29 AM

Summary

Original: Editing the avatar in Assets Object View throws uniq attribute error

New: Editing the avatar in Assets Object View throws unique attribute error

Sireesha made changes - 21/Mar/2023 9:27 AM

Description

Original: h3. Issue Summary Editing the avatar in Assets Object View throws unique attribute error. This is reproducible on Data Center: yes h3. Steps to Reproduce  # Create object type where two attributes have the constraint "unique".  # Go to the asset view screen  # Hit the edit button  # Add an avatar, and update.  # Hit the edit button again  # Remove the avatar  # Hit Update h3. Expected Results Avatar was removed and the asset was saved. h3. Actual Results The asset is not saved and both unique attributes throw the message "the attribute... has to be unique". h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available

New: h3. Issue Summary Editing the avatar in Assets Object View throws a unique attribute error. Editing the avatar from the object list view works without any issues. This is reproducible on Data Center: yes h3. Steps to Reproduce  # Create object type where two attributes have the constraint "unique".  # Go to the asset view screen  # Hit the edit button  # Add an avatar, and update.  # Hit the edit button again  # Remove the avatar  # Hit Update h3. Expected Results Avatar was removed and the asset was saved. h3. Actual Results The asset is not saved and both unique attributes throw the message "the attribute... has to be unique". h3. Workaround Currently, there is no known workaround for this behavior. A workaround will be added here when available

Sireesha made changes - 21/Mar/2023 9:20 AM

Component/s		New: Jira Service Desk [ 68207 ]
Affects Version/s	Original: Insight 10.0.7 [ 102901 ]
Affects Version/s		New: 5.2.0 [ 102196 ]
Affects Version/s		New: 5.4.0 [ 102903 ]
Affects Version/s		New: 5.5.0 [ 104101 ]
Affects Version/s		New: 5.6.0 [ 104395 ]

Load more older events