Media cannot be attached to comments and comments cannot be edited (Jira Automation)

[Matthew Pavouris]

The following issues are only present in tickets created with Jira Automation. [edit: we've determined that these issues are only present when the ticket is in "Closed" Status; there are no issues attaching media to or editing comments when the ticket is in "Open" or "Reopened" Status. This is a bug that Jira should address as we should be able to attach media to and edit comments while the ticket is closed.]

If helpful, I can post screenshots of what the Automation rule is, but there is nothing specifically pertaining to options for Comments or anything like that. The rule is to essentially clone an Epic and its child tickets.

Edit: Here are screenshots of the Automation rule. As far as I can see, nothing should affect the functionality of adding media to or editing comments, but let me know if otherwise. All the rule should do is clone an Epic and its child tickets (to be clear, nothing should occur in regards to comments being made or the functionality of comments):

---

Here is a screenshot of the audit log. The rule is always successful with no indication of issues with comments or anything else:

---

This issue was not present until a few weeks ago.

The "Add image, video or file" icon is missing from the Comments section (when typing a new post or editing a post):

This is what it should look like:

We are unable to paste media with Ctrl+V either.

We cannot drag media from a local folder to Jira either.

Clearing cookies for Jira doesn't restore the ability to add media. Neither does restarting the browser or the computer.

Another issue is that comments cannot be edited. The following happens when trying to save changes to an edited comment:

Has anyone come across this and what steps, if any, did you take to fix it?

Thank you

[Higashi]

Simple answer: You cannot.

Longer answer is that the URL split into few parts, that are handled by different Atlassian product components:

Here's how the parts of the URL are composed and used:

http://host.com:port - The operating system directs the request to the application server (e.g. Tomcat) that handles the specified port.
/refapp - Tomcat directs the request to the application refapp.
/rest - The application's deployment descriptor file (web.xml) maps the URLs to the relevant servlets.

/api-name/api-version - The REST plugin module takes over. The relevant part of the URL (api-name and api-version) are defined as the path and version in the atlassian-plugin.xml file. For example:

<rest key="helloWorldRest" path="/myrestresource" version="1.0">
    <description>Provides hello world services.</description>
</rest>

/resource-name - The final part of the URL mapping (resource-name and sub-elements) is done via annotations on the class, used to declare the URI path, the HTTP method and the media type.

If you'd like to have shorter URL, use single number version (ex. 1), and shorter path in your atlassian-plugin.xml file.