Did Trello (Atlassian) remove the ability to report bugs unless you're a paid member?

[Vongsawat]

Wow.

Going to the Support page there is no way to submit a bug report anymore, as going to "Technical Issues and Bugs" and then "Trello" is now a dead-end if you're not on a paid plan.

The docs are out-dated as well, as I was hoping they would point out where to submit a bug ticket, but its still giving the steps for the old support portal even.

Has there been any communication about the correct way to report a bug I've just missed? Or have they closed that off entirely? Or is reporting it as a Question in the forums is the correct way?...

(The bug is related to how Automation Variables react to links with @ signs in them, adding them to the description box adds bold formatting to it... again and again, such that you end up with https://www.youtube.com/user/@******************Trello**. But that's not really something the Community can do anything about.)

[Brittany Joiner · Accepted solution]

@Vongsawat they did announce this recently: https://community.atlassian.com/t5/Trello-articles/Changes-to-Trello-Support-for-Free-Plans/ba-p/2731367

if you want to explain the bug in here, as a community leader, I have an "escalate" button I can click and escalate it to support

[Vongsawat]

Forgot I threw up my hands at Trello not caring about bug reports. Never got around to "submitting a bug report" for you to escalate.

Here's simple reproduction steps:

1. new card with description https://www.youtube.com/user/@Trello

2. create a card button automation that just sets card description to {carddescription} (which if working properly, will do nothing, as it'll just replace the description with itself)

3. click the button and see that the Trello portion of the link is now bolded

4. every additional click adds **** between the @ sign and the bolded Trello

My understanding is, any Automation Variable that contains within it a link with an @ sign in it, will trigger this bug. Did a bit more work trying to pin down its specifics, but that was 4 months ago, so can't quite recall all of the bug's expressions.

---

Still find it kinda preposterous that the official way of submitting a bug ticket, especially in cases where its more of a consideration for Trello than the ones who trip over the bug in the first place, is to throw it in to the community forums now.

I'm guessing(?) that even though I "reported" this bug almost 4 months ago now, at the end of the above post, even without repro steps and all the bells and whistles, it just languished here and never got escalated? Either way, the bug is still live.