Backing up and restoring help needed

[Andy Nash]

I'm a (non-techie) admin on our instance of Jira Cloud.

A colleague has accidentally deleted a custom Story Point field which was in use by other teams.

I don't manually take backups of our Jira Cloud instance myself (and am not aware anyone in the organisation that does).

Is there some way to restore my Jira Cloud instance to a previous state, or does that require me to have manually taken a backup recently?

If there are regular automated backups available for me to restore to, are there instructions for doing so? I've only found instructions for what appear to be manually taken backups.
https://confluence.atlassian.com/cloudkb/how-to-import-only-part-of-a-jira-export-into-jira-cloud-859461966.html


If restoring from non-existent automated backups isn't possible, can anyone advise on next steps?

[Support Team [Clearvision] · Accepted solution]

Hi Andy

There is a trash feature on Jira cloud for custom fields so depends when it was deleted and/or if it has been deleted from the trash

See the details here https://support.atlassian.com/jira-cloud-administration/docs/edit-or-delete-a-custom-field/

[Andy Nash]

Many thanks, support.

I'd never come across that before. Very handy tool to catch such accidents!

[Andy Nash]

@Support Team [Clearvision] 

Should I expect everything to return to normal immediately after restoring?

Do I need to log back into Atlassian for changes to take affect?

[Support Team [Clearvision]]

Hi Andy

Yes it should be pretty instant. You can potentially search for issues that have a value for the field via

customfield is not EMPTY

where customfield is the name of your custom field

[Andy Nash]

Thanks again. Turns out the problem was multi-faceted and the deleted field was a bit of a red herring (though a useful thing to now know about!).

The actual problem was a disassociation of a field with a project, a re-association, but the visibility of that field in one of the layouts was hidden rather than showing by default.

We got there in the end (although I may be being too optimistic - I'm still awaiting final confirmation of this assumption!).