-
Bug
-
Resolution: Won't Fix
-
High
-
15
-
Severity 3 - Minor
-
Summary
When you have more than one task to check/uncheck in the same page it may be reasonable for you to click all of them very fast, one after the other. And when we do this fast check/uncheck of tasks in the page it will throw an error at some point and the task won't be checked/uncheked.
Steps to Reproduce
- Add some tasks to a page and save the page
- Start checking them one by one very fast
Expected Results
The checks/unchecks are saved.
Actual Results
At some point this will throw an error on top of the page:
Oops! Your task change couldn't be saved.
There could be a few reasons for this. Dismiss
Checking the browser's console you'll see a 500 error on the POST saying something like
Inline Task #3 was not persisted to CHECKED because of (status: error)
Notes
This can be reproducible on both old and new look. See screenshots for the errors
Workaround
None
[CONFCLOUD-56972] Checking/unchecking tasks very fast on a page gives error
Our company is affected by this issue. We are using Confluence for our manual software tests. The tests are defined on pages with lots of tasks to perform and then check if done.
Our users are complaining that after moving to cloud in April that they're running into this error a lot while testing.
I'm glad that this issue got reopened in March.
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Receiving the updates to this ticket today renewed my confidence in our firm's decision to migrate away from Atlassian products entirely. This is one prime example of why we switched. I was honest with my feedback in November and received a dishonest answer, and it's a good thing we didn't depend on the outcome promised.
I have a very similar problem (possibly the same), as I use a lot of checkboxes in a large table, which is the source for updating a plot.
I also have to refresh the page a lot of times to make sure all checked boxes are really saved, which is making the whole project nearly unusable.
Last comment is from December 2019, but 9 months later it is still not fixed.
EDIT: For the record: We use Confluence 7.4.0
matt.lyons1020787436 adrian45 – thank you very much for sharing your perspective and specifically for highlighting use cases that are important for your teams. Please don't hesitate to reach out in case of any issue, regardless of the severity.
As for this one - we got it prioritized, so it will be fixed within a sprint or two.
I would like to weigh in support, like Matt, to prioritize this issue to be fixed. Our primary application for Confluence is QA related and requires heavy use tasks in our documentation, and this is a massive drain on the productivity (and sanity) of people using those tools. At this point, I feel like the time wasted by team members encountering this issue far exceeds the time that would have been spent migrating our processes out of Confluence entirely. As the end of the year approaches and this issue will soon have existed for 3 months without visible progress (still parked at gathering impact), I'm considering that's really the only practical solution available to us now. After another afternoon spent repeatedly refreshing documents and scrolling back to my previous place myself, I am imploring you to somehow iterate progress on this issue because it singularly significantly degrades our experience with confluence at a basic functional level.
When it comes to the number of affected users, I can speak that in our case as our Confluence admin I reported and watched this issue but it is of course affecting more users than just myself on our team.
Edit: I also see the issue's Created Date is August 22nd, but Matt's comment dates from April. So I'm not sure just how long this issue has actually been tracked for, it may extend beyond 3 months.
It seems this could be reasonably easily fixed by debouncing the check/unchecks on the front end and/or queueing on whatever the exclusive lock is on the back end. I see that only 2 customers, including me, have reported this and there are only 4 watchers. I find that very hard to believe, as it is universal and quite easy to reproduce, but presumably this is because many users are simply mildly annoyed and frustrated by this and either abandon the feature or suffer in silence rather than report it.
Cheered to soon in my previous comment
Now this issue got closed as Won't fix.
Just today, another testing phase started, and I already got the first complaints that they cannot check their test tasks as done.