I disagree with this suggestion.

Why?

Because these accidental site creations should not be happening. This is something that Org admins should be able to prevent from happening to begin with. Why are we fighting to have an extra checkbox added to the subscription cancellation screen? Just stop allowing it to happen, Atlassian.

"How can Atlassian better support your organization?"

That is the title of an email from Atlassian, which you have probably also received, containing an invitation to "Share your thoughts in a short 5-7 minute survey".

I recommend everyone to participate and share your thoughts about Atlassian pushing shadow IT towards the managed users of customers with Jira Premium and Confluence Premium.

During the survey, there are 3 text boxes where you can type free text. Keep Atlassian informed about your thoughts!

Since it's highly unlikely Atlassian is going to add a new Cancellation reason that would acknowledge their broken login workflow that causes accidental site creations, what if we all agreed upon a hashtag that Atlassian could easily search on?

How about #accidentalit ?

Hm. I kind of like how that sounds like "accidentally" which is how all of my users created their sites. :-{

(For reference: https://community.atlassian.com/t5/Articles/How-to-Discover-Rogue-Accidentally-created-Atlassian-Sites/bc-p/2853525#M538)
 
 
Tagging e464a36bba8f who requested this feature.

This is a great idea for a ticket, because... data, right?

Here, I can help. We migrated to Cloud in May 2024. This required people to learn a new URL for Jira and Confluence. 

Unfortunately this also means that people forgot that new URL, and we have since had 41 SITES created by mistake.

That's 41 sites for which I've had to: 

• Notify the user who created the site, and confirm it was a mistake (100% have been mistakes).
• Make myself admin of the site.
• Request cancellation of the site.
• Open a ticket requesting expedited cancellation and deletion of the site so I do not have to wait for 30 days or whatever the minimum is these days.
• Confirm in the ticket that I really really want to delete the sites and DO NOT want to rename or swap them with other sites.
• Wait a minimum of 14 days for the site to be deleted.
• Remember to go back on site deletion day, confirm deletion, and then delete the organization.

I have an Excel sheet tracking all of this:

Instance, Product, Creator, Notified (Y/N), Support Request (link)

Date fields:

Created, Instance Cancelled, Request Filed, To Be Deleted, Org Deleted

Very interested in automating all of this or better still, Atlassian fixing it.

If Atlassian refuses to prevent users that already belong to a company's organization from creating sites then at least this solution would help Atlassian track the number of sites that admins have to continuously clean up because users don't know any better. Hopefully they realise soon how big a problem this is for organisations.

Yes, I'm having to clean up accidental sign-ups.  This issue is creating additional administrative work and opens the platform to abuse.

Previously Atlassian Support resource advise I fix the problem with end user training.  That'll only go so far.  If more training is the only solution, seems there is an opportunity to make the product a little more intuitive.