288
Custom Statuses
under review
Activity
Newest
Oldest
Duncan Hamra
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.
Jason Adams
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.
Guillaume Cougard
@Jason Adams: I couldn't agree more, our users need to know that it will "soon be released", not only that it is already available...
Tupper
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.
K
Ken Greeff
Would like to create custom statuses as well
Kevin Hoffman
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.
Tim Soulo
+1 I would love to tag some feature requests as "unlikely"
:trollface:
Nihoul Victor
That's a needed feature. For my case (program development) it will allow me to make bug tracking inside Canny too.
Lucas Dailey
The major status I'm missing is "Tracking". For items/requests/ideas that are worthwhile (therefore don't go to "Closed") but aren't "Planned". This is one of the biggest categories for a startup. There are innumerable good things to do. If you narrow it down to even the best ideas you'll still only be able to plan some of them. So what to do with the rest? Track them. You're waiting for more info, gathering more data, digging deeper, etc. Track covers it all.
N
Nick Kwiatkowski
I personally would like to see things like "Accepted", "Researching", "Under Review", "In Development", "Waiting for feedback", "Released", "Declined", "Deferred", or "Available with Work-around".
Ultimately, each customer should be able to setup and use which status that work best for their situation. I'm sure the ones I've listed won't match what other people want. Some of the defaults I would want to hide since they don't make sense for my customers.
I would be fine with different statuses per board, or not. We only have one board, but if we had more, I wouldn't imagine that we would have different ones.
Sarah Hum
under review
We know this is a popular request so it's now under review by our team. Thanks to all that have shared thoughts already. If you have insights to share, we'd love to hear it.
Couple specific questions:
- Do you just want to rename the existing statuses or create new ones? If the latter, what are examples of statuses that you'd create?
- Do you want different statuses per board?
Kris (AMS)
@Sarah Hum: Ultimately being able to create new ones would be cool. I'd like to have a "Declined" status for things that won't be done , ever. Different statuses for different boards would be handy because a bug reports board would include "Fixed".
Sarah Hum
@Kris (AMS): Hi Kris, any reason the "Closed" status doesn't work for "Declined"?
Kris (AMS)
@Sarah Hum: Different meanings.
Aev
@Sarah Hum: Whoa, love to see movement on this!
- Ideally, both. Having the existing set as the "default" but being able to change them and add/remove would be amazing. "Ongoing Investigation" "Gathering Information" "Not Currently Possible" "Declined" "Expected Q3" "Workaround Available" "In Beta" "Needs Reproduction Steps" "Fixed" etc.
- Yes, definitely. The context of our posts can be very different depending on the board. Feature Requests vs Bug Reports vs Feedback, etc.
Kevin Reid
@Sarah Hum: for a features flow, I think the current options are great. For capturing bugs, it might be a little different. We currently use "Under Review", but I think "Acknlowedged" would be more appropriate. Other statuses that could help would be "More Info Needed" or something similar. I think we'd be okay with all boards having the same statuses, but it would be interesting to have board-specific statuses as well.
I'm not sure how many other Canny customers use it for bug reporting, but perhaps a "bug scheme" of statuses could work as well, with a separate flow.
Sofía Ríos
@Sarah Hum: I think the more flexibility you allow, the better. As for your questions:
1) I want to create new statuses, for example, "Waiting for Feedback" or "Declined"
2) It's not a must for me.
Trent Maynard
@Sarah Hum: Create new ones. Don't care if there's different statuses per board.
Thomas Perkov
@Sarah Hum: Would also like to specify which are shown in the public roadmap. Currently we don't want to show all 'completed' and need use 'closed' instead.
Kevin Hoffman
@Sarah Hum: Our team is definitely feeling the need to differentiate between "Completed" (the change has been merged) and "Released" (the change is available to the public).
Currently we keep feedback "In Progress" until the change has actually released because we don't want to mislead users into thinking the change is actually available to them. However this makes it difficult to internally track which changes have been completed from a development perspective.
D
Dave Brown
@Sarah Hum: Perhaps a middle ground would be allowing us to create aliases that map to your standard statuses... For example, maybe I want end users to see "declined" or "resolved" but they are both "closed" as far as the backend and reporting would be concerned.
As a product owner, I need to be able to communicate statuses that align with our company's lexicon and dev process, so that end users feel that we are listening to them and valuing their opinions.
As an idea contributor, I want to see the status of an item in plain english, so I can understand where an idea is in the process and feel validated.
Procore and Azure Devops have this approach for parts of their tools.
Sarah Hum
Thanks for your thoughts @Dave Brown! I get the reporting side of things.
Re: communicating to end users, you are able to include a comment with the status update to explain the change. Does that work for you?
D
Dave Brown
@Sarah Hum: A comment would work for explaining the change. Being able to show incremental progress, even if just a "branding illusion", would go a long way towards validating my end users AND providing more frequent updates to keep them engaged. I would probably never need to report on statuses any more granularly than the standard ones but if I were able to break out "in progress" to custom states like scoping, gathering feedback, partially complete, etc that allowed for more frequent updates it would have a positive impact on people that supported the idea.
As a product owner, I want to have more granular statuses along the development lifecycle, so that I can frequently communicate progress to my end users and keep them engaged.
As an idea contributor, I want to see my idea changing status along with comments, so that I get the feeling that work is progressing and that my feedback is contributing to that progress.
Baffour Atuah
@Sarah Hum: I second what Dave's saying! You want the statuses to match the terminology you're using elsewhere. And our features are less likely to have quick turnaround times where we review, and then just start doing stuff. So it'd be great to have more granularity. E.g. prioritised, user research, design, in development.
Much like other ticketing tools!
Load More
→