It can't be based on the age of the post, as sometimes an older post will be editable while a newer post is not.
It can't be based on whether the status was changed by the CIQ team, as sometimes a post whose status was changed is still editable.
It can't be based on the age of the post, as sometimes an older post will be editable while a newer post is not.
It can't be based on whether the status was changed by the CIQ team, as sometimes a post whose status was changed is still editable.
e.g. This new bug report is no longer editable:
This slightly older bug report, whose status has been changed by the CIQ team, is still editable:
After looking at a few posts, it looks like as soon as somebody votes on your bug report, it's no longer editable.
Yes, I knew that. Otherwise I could edit the request for adding sleep related data to the SDK (with 440 votes) and change it to something different.
But hey, let's be realistic, what would that matter? It's not that Garmin would "accidentally" implement something else for x-mas instead of what 440 people wanted.
I suppose that makes sense. I looked around in the options and the admin tools to see if I can change this behavior and there's nothing I was able to identify to allow editing once something has received a vote (there are no options I can find related to editing in any way).
Not to state the obvious, but I'm not looking to deceive anyone, only to have the ability to fix typos and make updates, same as we can before a vote is cast.
I'd guess that Garmin can see the original idea (but maybe not), and if there's a concern about users being tricked, maybe the forum could give people a way to see the original idea and/or the edit history (but maybe not).
Also, I found that the non-editable state is *not* permanent.
e.g. If I vote on my own bug report that previously had 0 votes, then it's no longer editable (because it now has 1 vote). If I remove the vote (so it has 0 votes again), it's editable once again.
Idk that's kinda hilarious to me but also totally expected