nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

A way to recover asset deleted in issue.

Sandro Santos

Hello, a user accidentaly deleted a bunch of assets. The assets were recreated, but the issue were the assets were used are left with an empty field.

Does anyone know a way to recover the information from the issues? There are now thousands of issues with an empty field. Is there a way to recover the information and restore? Through bulk change or automation?

Accepted answers

Steve S_

@Sandro Santos there is way to see what was changed in a ticket outside of the History tab available to the user. You can view the changelog of a ticket via a Send web request. That said, it sounds like even if you get the changelog of a ticket, because you have so many tickets impacted this solution is not very practical.

I recommend using Ask Rovo to guide you in setting it up if this is new territory to you. But it will generally go something like this:

GET https://<your-atlassian-site>/rest/api/3/issue/{{issue.key}}?expand=changelog

Now you have a smart value like {{webResponse}} and all the dot notation capabilities that you can utilize like {{webResponse.body.fields}}, {{fieldChange}}, etc..

Not really a direct fix to your issue but I hope this gives you some ideas.

All comments

Connor_l49hkb

Hi @Sandro Santos I think you might be out of luck. I tested deleting an asset that was linked to an issue and then checked the issue history. Unfortunately the deletion wasn't recorded in the issue history. There was nothing listed in the Jira audit log either.

Arkadiusz Wroblewski

Hello @Sandro Santos

First one questions. Deleted was an Assets Custom Field Values or Assets itself? If Assets Custom Field, value must show up in Issue History (that also happened to me).

Coming back to main Topic.......

Jira lacks an automatic way to restore these values. Deleting the original Assets objects destroyed their unique references. Recreating objects with identical names generates entirely new IDs, so the old issue links cannot automatically reconnect.

Recovery requires finding a historical mapping source. Check older Jira backups, external CMDB exports, or the issue history changelog for the old values. Once you establish a mapping, update the fields in bulk via CSV import, the REST API, or Jira Automation.

Without a backup or history log, Jira cannot automatically pair these issues to the new objects. Contact Atlassian Support regarding the scale of this issue, though a selective backend restore is unlikely.

Best,

Arkadiusz 🤠☀️

Marc -Devoteam-

Hi @Sandro Santos

If asset objects are deleted, they can't be recovered.

Recreating them will give them a new ID. So issues that used the old objects will not get the values back.

You will need to update the fields on the related issues one - by one or in bulk, depending on the object used and number of issues.

Steve S_

I recommend using Ask Rovo to guide you in setting it up if this is new territory to you. But it will generally go something like this:

GET https://<your-atlassian-site>/rest/api/3/issue/{{issue.key}}?expand=changelog

Now you have a smart value like {{webResponse}} and all the dot notation capabilities that you can utilize like {{webResponse.body.fields}}, {{fieldChange}}, etc..

Not really a direct fix to your issue but I hope this gives you some ideas.

Sandro Santos

Hello, @Steve S_

This was what we ended up doing, but with Codex. Was a lot of work, but we managed to retrieve the infomation we needed.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management

assets