Bug in Jira

[Kishore Srinivas]

I noticed an issue/bug in Jira while uploading evidence in the comments section. I use tables to update scenarios and evidence as part of my testing role, and recently attaching images has been failing. This is not due to image limits, because if I cut and paste the entire table into a new comment, I am able to attach images. If that doesn’t work, logging out and logging back in fixes the issue temporarily.

I am facing this issue at least 5–6 times a day, and it is not convenient to log out and log back in each time. Could you please help find a solution or raise this concern with Jira support?

[Dan Breyen]

Hi @Kishore Srinivas I took a quick look on Atlassian's Jira Site and didn't see anything specific for this issue, but you're more than welcome to search for yourself. Just for troubleshooting purposes, do you know if this is something that you can recreate at will? (I'm probably interpreting your steps differently) Does this happen for other users?  Have you tried this in different browsers (Edge vs Chrome).  

I tried it briefly, and couldn't get it to fail.  I will flag Atlassian Support to take a look at this.  With your Premium License, if they don't get back to you in a few days, I'd open a new Work Item with them and provide them with as much detail as possible.

[Kishore Srinivas]

Hi Dan,

Thanks for your response.

I am from the IT team in our organization, and this issue is currently being faced by one of our team members. The issue is reproducible on his end and occurs frequently during regular usage while working with tables in Jira comments.

So far, we have validated the following:

Issue occurs across browsers (Chrome and Edge), including Incognito mode
Not reproducible consistently for all users, but persistent for the affected user
Attachment option (including paperclip) gets disabled
Issue persists even with minimal table content (3–4 rows)
LastPass extension was disabled, but no change observed
Paperclip workaround also does not allow file selection

We have coordinated with Jira Support and shared all findings. As per their guidance, we are currently in the process of capturing HAR file and console logs for further analysis before they can proceed with creating a JRACLOUD bug ticket.

Additionally, we are observing the following errors in the console:

“Uncaught (in promise) TypeError: e.update is not a function”
404 error on user properties API call

We will share the HAR file and detailed logs once captured. Please let us know if you would like any additional information from our end in the meantime.