No error message when unable to upload worklog items (because limit has been reached, HTTP 413)

[mlemoine-clgx]

Checklist before you being

• I am sure that I am already using latest version of Jira Assistant
• I had verified that, no similar issues are already reported in issue tracker
• I had tried reproducing this issue with with Web version of Jira Assistant to ensure that this issue is not recently fixed and yet to be published
• I had verified that, my query is not answered in FAQ section of website
• I had verified that, my issue is not listed as known bugs in website

How do you use Jira Assistant?

Web version

Are you using cloud version of Jira or self hosted (data center / server) of Jira.

Cloud Jira

Version of Jira Assistant

2.6

What browser are you using?

Chrome

What OS are you using? You need not disclose this if you feel it is irr-relevant for your issue.

None

Bug Description

Prerequisites:

• A JIRA Task with the maximum amount of worklog items (10k, but YMMV, when trying to log more time in JIRA, we see the "We can’t log any more time on this work item as the limit as been reached." error message

Reproduction steps:

1. Log time (check "upload immediately") on that Task
2. Click "Submit"
3. "Add worklog" dialog remains on screen, no error message in the UI, worklog item does not appear in Worklog Calendar, Worklog Report, or JIRA. DevTools's network tab shows HTTP Status Code 413 for the upload request.

We have some JIRA stories/Task that sometimes reach the maximum number of worklog items (10k).
When that happens, we have no feedback from JIRA Assistant.

I am configured with "upload immediately" and the "Add worklog" dialog just stays there, with nothing happening when clicking on Submit.

While I don't expect JIRA Assistant to be able to bypass JIRA's limit. Some explicit error message would so much less confusing, especially since that's not the kind of issue that happens often, but when it does, it could impact many users. In our case, the Task is a generic "Meetings during Year X" Task used for time tracking. The whole team is using the task for time tracking, so everyone will be impacted.

Checklist before you submit

• I have ensured not to paste any confidential information like Jira url, Mail id, etc.
• I have verified my browser console logs and added necessary details (if required)
• I have added required screenshots if the bug is related to UI (as necessary)

[github-actions]

Hi @mlemoine-clgx, thank you for your inquiry regarding the lack of error messages when the worklog item limit has been reached. Your experience of encountering an HTTP 413 error during the upload process is indeed frustrating, and I understand the confusion it may cause when feedback is absent from the UI. It seems your situation shares similarities with existing discussions about proper error handling when limits are reached. Specifically, this connects closely with Ticket #241, which addressed error messaging during worklog uploads, albeit in a different context. I will ensure your feedback is noted and brought to the attention of our team as we value enhancements that improve user experience. In the meantime, could you please provide any screenshots or additional details about the occurrence? This will help us in further investigations.

---

Disclaimer: Please note that this response has been generated automatically by an AI bot. While we strive for accuracy, there may be instances where the information is incorrect or inappropriate. We review these responses periodically and will make necessary corrections as needed. We appreciate your understanding.

[mlemoine-clgx]

Specifically, this connects closely with Ticket #241, which addressed error messaging during worklog uploads, albeit in a different context.

I did see this ticket. Since the exact reason the worklog was not uploaded is not mentioned in #241, my issue is a different status code, #241 was implemented back in 2021 and my issue still showed up, I think it's a different problem.

But having the worklog items show up in JIRA Assistant without being uploaded (along with the error message) would be great. It would allow us to easily change the JIRA Task we are logging Task against once a new one has been created.

In the meantime, could you please provide any screenshots or additional details about the occurrence? This will help us in further investigations.

I am not sure what more would be needed. I'd be happy to provide data and screenshot if there are any specific requests.

[github-actions]

Hi @mlemoine-clgx, thank you for your detailed response. Your insights regarding the different error status and the need for improved messaging when worklog uploads fail due to limitations are highly appreciated. We recognize this as a unique issue that warrants individual attention and can enhance the user experience. I will make sure your request for explicit error messages and visibility of uploading failures in Jira Assistant is escalated to the development team. If you have any specific scenarios or examples in mind that you believe would illustrate your point further, please feel free to share them. We are here to help!

---

Disclaimer: Please note that this response has been generated automatically by an AI bot. While we strive for accuracy, there may be instances where the information is incorrect or inappropriate. We review these responses periodically and will make necessary corrections as needed. We appreciate your understanding.