Yeah, that's right. Before we escaped JIRA, my team would often do that, too, even for regular sprints. Make a checklist in a collaborative editor tool like Google Docs or Notion, and just do the day to day work there.
Then somebody would have to copy it to JIRA so the work would get tracked.
But very little of the planning, work breakdown, day to day updates, or discussion actually happened on JIRA because it was literally like a hundred times slower (with the convoluted UI compounded by incessant "wait... is it even loading?... oh, OK, it finally loaded" at each step of the way).
I manage a team of devs but my clients love to use Jira. So I typically use something like Board Genius to sync between Github issues and Jira. This also let's me keep my devs out of Jira so they can just focus on actual work and not worry all the discussions that happen in Jira between my clients and project management.
2. It is dog slow.
3. It is dog slow.
...
When my team had an important as-quickly-as-possible sprint, we dropped Jira and switched to Google Docs as it was much easier and faster than Jira.
My conclusion was that Jira doesn't do much for developers that can't be done in some Google Docs/Sheets.