This is pretty much needed!

We really need this one. I manage requests from colleagues on what we should be adding to our product.

Generally how it works is it starts with the OP submitting their idea/post, so it has a status of Open.

From here there's discussion back and forth, either on Canny or in meetings to get to the heart of the problem and the impact working on it would have.

So, in some cases I ask the OP and/or other people for more info in the Canny post. There is no easy way to mark this post as requiring info, for now I leave it Open and give it a tag which is messy. I need a new status for this as I need to review my board on a daily basis and see which ones need my input. I need to filter these posts out where I'm awaiting information from someone else and the tag solution isn't great

Another example would be that I assess an idea, understand it fully, but it won't be taken further for now as we don't have anyone to work on it. In that case it's not 'Under Review' because we use that status to mark ideas we're bringing forward for discovery and/or development. It needs to be a status before that where it's on hold for now - not open and not yet under review.

We really need the option to add other statuses as we use all of the existing ones but also need other ones that fit in between the existing ones.

This limitation is starting to become a huge issue for our organization and how we communicate with our customers. We've had to start looking at alternative solutions because this issue isn't being addressed.

I would also like the ability to create custom statuses: change the label of existing/pre-built ones and create additional ones (eg: "Good Idea, keep for later"). It can be a Setting for all boards. I should be able to select which Statuses I apply to each Board. Thanks ! Canny Rocks!

Hi team! Amazing work on Canny. You've done a fantastic job creating a tool which seems to do everything I need while keeping it simple to setup.

I understand why you might not want us to add additional status's but I don't see why being able to change the name of status would increase complexity when it comes to onboarding and support? The words we use to communicate the status of a feature request are oh so important, and I'm not confident the defaults are going to do it for us.

I know it seems small, but under review, planned, closed, can all mean different things to different people. Especially people who are doing time sensitive work for clients. I'd really like to be able to change the wording. In a perfect world, I'd be able to add a description that sets perfectly clear expectations.

We are also running into this limitation. We need a way of distinguishing between a bug/feature request being finished by our dev team, versus actually being released. If we marked it as "completed" then it appears to voters as though it's available for them. Right now, we leave it as "In Progress" and then add a tag to indicate the release it's in, but a custom status would be the best solution.

Would _love_ this feature. We have tons of requests that aren't really appropriate to put into "under review", but rather "considered" or something along those lines.

Would also love to have something like "Won't Fix" or etc. Just a bevy of things. Would also love to be able to customize depending on the board. Probably my most-desired feature.

Would like to create custom statuses as well

The inability to add additional statuses is making it very difficult for our team to distinguish between feedback that has been "Completed" versus feedback that has been "Released" and is available to our customers.

This causes us to keep feedback "In Progress" longer than necessary which leads customers to think that a bug fix has has not been resolved. We are increasingly seeing customers reach out to ask if feedback has been addressed when it's actually merged and ready to ship.