Your gif actually shows that the feature wouldn’t really help too much, since it currently already shows “similar to” topics when making topics through the native Discourse post editor:
A caveat is that I think this is less visible on mobile, so maybe a lot of the users are posting from mobile.
Regardless this is still valuable, it will help a non-0 amount of users find similar bug reports, so we will tackle this problem in some shape or form. (maybe not exactly like above but definitely some way to see bug reports that are close to what you are reporting, or maybe a list of recently reported issues in the issue area you selected)
Compared to a couple years ago we have a lot more tools internally to make sure we’re addressing issues. For example we now assign an owner internally to each issue to make sure they get looked at in due time.
Give the system a roll for some weeks and let us know in #forum-help:forum-features if you don’t see a satisfying response so we can take that to the teams internally and see how we can improve that.
There’s no point in having a separate “Regular” trust level once we move over permission management to the devforum groups. You can see the trust level distinction between users vanish in the near future. There’s no point in having a separate “Regular” trust level anymore at that point, it has never actually meant the user is a “regular” forum user anyway.
Question, if you get accepted, will there be a notification ping like if you join a beta group? I’ve got activity from people @'ing bug report group, but it seems like I’m not in it which is weird.
By request message, do you mean request to join the Group?
You can try to submit again if you’re not sure that it went through. It’ll pop up with a window that says You have already requested membership for this group. if you already have. You can also check your Sent folder in your Messages
To add what Hooksmith said, the trust level status has mainly been used to manage who can do what on the forum. Changing how we manage permissions means there won’t be a reason to maintain the old Member and Regular distinction — I’m curious if it’s something people would enjoy if it was purely a cosmetic badge on the account?
Some feedback, whenever you already applied for the group, you don’t know if you already applied unless you send in another application, and whenever you hit “submit”, it’ll error with “You already applied”.
Could we get a “Pending” on the group page, please?
Thanks for the replies, I personally don’t care about the title / a profile badge but some channels were locked for non-regulars, and since post-approval got paused for a while, it’s left me with fewer options to pass on things like bug reports, which meant I had to directly contact developer relationships before (one example being during voice chat beta testing that went back and forth for a while), if this new system fixes all that / streamlines it then I am more than happy with the change.
I believe that if benefits are to be provided to level 2 “Regular” members that the most important pre-requisite would be the improvement of ranking-up for existing creators and members. The process to getting the “Regular” status seems completely arbitrary with no clear process of obtaining it.
I never knew that Discourse had that. Although this is a forum, it’s quite silly to expect people to read. At the same time, users who are creating topics in #help-and-feedback:scripting-support are in a vastly different headspace than those creating #bug-reports. Thus, they are more inclined to overlook or acknowledge but ultimately ignore this passive warning.
extra context
When I was making this gif, I observed multiple instances of someone creating an “Attempt to index nil with…” topic, having it solved, and then creating another topic with that exact same prefix. The only difference being:
A) the value after “with”
B) the line number/script where the error occurs
C) Both A and B
This is unrelated to bug reports, however, this should maybe be addressed.
