FEATURE REQUEST: Don't erase what I typed if I accidentally click away while adding a comment

[Rob Bl]

Please change Confluence so that users don't lose everything they've typed in a comment if they happen to accidentally click outside the comment UI. I just lost a carefully composed comment reply in which I was being extremely precise about my wording for the sake of clarity, and now I have to start all over. This has happened to me at least 10 times in the last couple weeks. It's aggrivating!

[Marc - Devoteam]

Hi @Rob Bl

I like you suggestion, but If you want this feature investigated or looked at, please raise it here:

Atlassian

This Jira instance is a public Atlasisan instance where possible bug, or features can be raised, you might search it as there might be an issues, related to your request.

[Rob Bl]

What a convoluted mess of a UI that site is! I can't even figure out how to search to see if this issue has already been reported.

[Rob Bl]

When I try to create a bug report, it routes me back to the Community.

When I try to create a ticket, I get shoveled off to https://support.atlassian.com/contact/#/

...when then shovels be back here.

[Marc - Devoteam]

Why trying to raise a bug?

It's not a bug, this ia currently and as it has been ootb. So raise a suggestion or support request.

Routing here (https://support.atlassian.com/contact/#/) gives you the opportunity to raise a technical issue. this doesn't reroute, except if you you a free tier option as that doesn't allow you to raise a support issue

You see this "imperfection" as a bug, but it's functionality that doesn't exist.

[Rob Bl]

I wasn't trying to report it as a bug. Should have just said "ticket." Bad choice of words on my part.

I was just trying to figure out any way at all to see if a ticket existed, and couldn't figure out how to do that (and BTW, I work in UI/UX/QA, this isn't me being in over my head), so then I went to https://support.atlassian.com/contact/#/, and the only option I'm given, even before I put in the URL of my project, is an [Ask the Community] button, shoveling me right back here.

I'm a consultant on the project, with limited access, so maybe Atlassian doesn't recognize me as significant enough to warrant actual support access. But I don't think it should be necessary for me to contact my client and ask them to pretty-please contact Atlassian on my behalf about the ways in which Atlassian is making my work for them difficult. (This is one of many time-sucking hassles in Confluence and JIRA that slow me down.)

But it sounds like that's probably my only option, unless I'm missing something.

Thanks for trying to help. I apologize for my frustration coming out here. Atlassian tools are about 70% fantastic (especially for a web app!), but of that last 30%, 25% are problems that are a) frustratingly obvious, b) should never have made it to production, and c) based on what I see in the Community, problems Atlassian has little interest in fixing. Of course, none of that is your fault. :)