---
title: "CMJ - Unable to apply change feature: avatar"
canonical: "https://support.appfire.com/space/SUPPORT/1258062717/CMJ%20-%20Unable%20to%20apply%20change%20feature%3A%20avatar"
format: markdown
---
This article explains the errors encountered due to the data corruption in the avatars folder.

> ℹ️ ### Environment
> ℹ️ 
> ℹ️ - **Jira**: Data Center
> ℹ️ - **App**: Configuration Manager for Jira (CMJ)

> Macro (aura-tab-collection)
> 
> > Macro (aura-tab)
> 
> When importing a project snapshot into a Jira instance, users may encounter the following error:
> 
> ```
> java.util.concurrent.ExecutionException: com.botronsoft.jira.rollout.snapshot.SnapshotOperationFailedException:
> Unable to perform deployment: Unable to apply change
> 'type: change, old value: bug.svg, new value exclamation.png,
> target object: JiraConfigurationRoot#root/JiraIssueType#risk:issueTypes, feature: avatar'
> ```
> 
> > Macro (aura-tab)
> 
> The issue occurs because of data corruption in the avatars directory. The files in the directory do not match the required naming convention:
> 
> > ℹ️ ID_[size]_FILENAME
> 
> This problem typically occurs when upgrading Jira from a version earlier than **6.1.7** to a version equal to or later than **6.1.7**. If the avatars directory from the previous instance is not properly migrated, Jira’s upgrade tasks fail to rename files correctly, leading to inconsistencies.
> 
> The** avatars directory** under <jira-home>/data/avatars was not synchronized with the Jira database during an upgrade or migration. As a result, avatar files have invalid names or are missing expected formats.
> 
> This aligns with Cause II, as described in Atlassian’s official article '[Restore Missing Custom Avatars After Jira Server Upgrade or Migration](https://support.atlassian.com/jira/kb/restore-missing-custom-avatars-after-jira-server-upgrade-or-migration/),' on restoring missing avatars after a Jira upgrade or migration.
> 
> > Macro (aura-tab)
> 
> 1. Run the following query on the Jira database to list avatar file references:
> 
> > ℹ️ SELECT id, filename FROM avatar;
> 
> 2. Confirm that the files in  `<jira-home>/data/avatars/`match the expected format: `ID_[size]_FILENAME`.
> 
> > 📝 In some cases, files may include extensions like *jrvtg.png, indicating they were upgraded from an older Jira version.
> 
> 3. Correct any mismatched filenames in the avatars directory to match the expected format: `ID_[size]_FILENAME`.
> 4. Ensure both **source** and **target** Jira instances use valid avatar filenames.
> 5. Once the avatars directory is fixed, create a new snapshot and re-run the deployment.
> 
> > ℹ️ - **Filename Format:** Files in the directory should follow the pattern `ID_[size]_FILENAME`.
> > ℹ️   - **ID:** The identifier from the database's `id` column.
> > ℹ️   - **[size]:** A suffix indicating the image dimensions (e.g., `xlarge`, `small`).
> > ℹ️   - **FILENAME:** The base name from the database's `filename` column.
> > ℹ️ - **Example:** If the database record is `ID: 10647` and `filename: profilePicture.png`, you should see multiple files such as `10647_xlarge_profilePicture.png` or `10647_small_profilePicture.png`.

### Related articles

> Macro (contentbylabel)