User scan not edit issue description

[Suzhou Liu]

We encountered a problem. Some users reported errors when editing the JIRA description, but some accounts can edit normally for the same issue,but he/she can edit other fields except description,the message like this:

{

    "data": {

        "jira": {

            "updateRichTextField": {

                "success": false,

                "errors": [

                    {

                        "message": "INVALID_INPUT",

                        "extensions": {

                            "statusCode": 400,

                            "__typename": "GenericMutationErrorExtension"

                        }

                    }

                ],

                "field": null

            }

        }

    },

    "extensions": {

        "gateway": {

            "request_id": "901546d0-c68b-484c-9985-6e1766f69976",

            "trace_id": "406796d95948414ba0dc9e0af61167dd",

            "crossRegion": false,

            "edgeCrossRegion": false

        }

    }

}

i have idea about this.  We have discovered that when adding an image through the Jira API and applying it to the description, some users are unable to edit it on the Jira page.

[yoppy rizaldi]

# Analysis of JIRA Description Editing Issue

Based on the information provided, there appears to be an issue where some users can't edit the description field in JIRA, particularly when the description contains images added via API, while other fields remain editable.

## Key Observations:

1. **Error Pattern**: Users receive an "INVALID_INPUT" error (HTTP 400) when trying to edit the description
2. **Selective Impact**:
- Some accounts can edit normally while others cannot
- Only the description field is affected (other fields remain editable)
3. **Image Correlation**: The issue seems related to images added via JIRA API in the description

## Potential Causes:

1. **Permission Issues**: The users experiencing problems might lack specific permissions for rich text editing or image handling
2. **Content Formatting**: API-added images might create formatting that the web interface can't properly handle for certain users
3. **Browser/Render Issues**: Potential inconsistencies in how different users' environments render the rich text editor
4. **Caching Problems**: The description content might be cached differently for different users

## Recommended Troubleshooting Steps:

1. **Check User Permissions**:
- Compare permissions between users who can and cannot edit
- Verify "Edit Issues" and "Attach Files" permissions

2. **Inspect the Description Content**:
- Examine the raw HTML of problematic descriptions
- Look for differences in how images are embedded

3. **Test Different Scenarios**:
- Try editing descriptions without API-added images
- Attempt edits with different browsers/accounts
- Check if clearing cache helps

4. **API Investigation**:
- Review how images are being added via API
- Compare with manual image addition process

5. **JIRA Logs**:
- Examine server logs for more detailed error information
- The trace_id provided could help track specific requests

## Potential Solutions:

1. **Adjust API Image Handling**: Modify how images are embedded via API
2. **Permission Adjustments**: Update role permissions if needed
3. **Content Cleanup**: Create a script to reformat problematic descriptions
4. **JIRA Update**: Ensure you're running the latest JIRA version with all patches

[Suzhou Liu]

inorder to display image in description, i use this methods when edit issue

{
"attrs": {
"type": "external",
"url": "xx"
},
"type": "media"
}

According to the official documentation, this approach is not recommended and may be the cause of the above error. But I don't know if there are any other better ways to do it.