Enter your idea

"I have just read another closed thread, about community users votes having increased to 10, so am starting this new one as suggested by Brittany in that closed thread...

I don't go looking for features to vote on, but do search community for existing conversations on anything I am having issues with in Xero, either for answers on overcoming it, or to vote on an improvement to something that is directly impacting on efficiency of my staff and functionality we use in Xero.

I have just exhausted my 10 votes, didn't know I had a limit til then.
I manually took a vote off a feature, which is now in planned status...so I could vote on a new issue which is important (it was already @ 25 votes).

How will issues get to 50 votes, the point at which Xero will look to make changes, if you cannot add a vote at any given time, to what is important to, or directly impacts on, the user?
Therefore, I agree in part with another voter in that closed thread, that

Votes should be returned to users, from any feature that changes to status of Started, scheduled, submitted
I would leave votes on requests marked NEVER, as I do believe that once enough accumulated votes are collected, that comment could change....and if you have to remove a vote from one of those requests, it defeats the purpose of having the ability to vote in the first place...

"