+1 I was looking for this functionality in the admin before realizing it wasn't possible.

We use Canny for our feedback site with around 9.4k users. Currently, we use Canny primarily for public bug reports, and also use it for feature requests or feedback. For bug reports, we take those reports and post the issue internally, cross-linking using Internal comments (thanks for that feature, love it!)

However, some statuses make no sense for bug reports-- "Planned", for instance, is nonsensical in that case. In addition, we run a rolling beta, where its important to indicate that an item is technically complete, but not available in our main branch yet.

It would be incredibly useful to have custom statuses so we can define things like:

- "Won't Fix"

- "Unable to Reproduce"

- "In Beta"

- "Not A Bug"

etc...

We use "Under Review" to indicate that a bug has been moved to internal tracking, but that wording isn't exactly right. I'd rather have "Tracking Internally" or etc.

I would imagine implementation would be something like defining the name of a custom status, a color, and then what to treat that status as: an open issue (still working on it), a closed issue (work will not be done for X reason), or a completed issue (work completed and issue addressed).

This would greatly increase the breadth and scope of projects Canny can be employed for.

We have a status of "Pilot", where a feature is released but in BETA for a select group of users, would be great to have this status, as the feature isn't "Complete" until it is out of BETA and released to the rest of our network.

I want a provision to help my customers understand when is the feature planned for go live. Example 'Planned in Q1' 'Planned in Q2' etc.

I'm curious what the rationale is for set statuses as opposed to allowing custom ones. For example, I could see how marking something as Alpa or Beta could be useful in some cases or planned for Q3, etc.

@sarah-hum:

As it happens the statuses are actually pretty much OK for me.

But...depending on the product/service an org has the statuses can be significantly different to the standard ones provided in Canny.

The simplicity is nice and maybe it just has to work for a lot of folks. But not being able to be more granular /change these will affect future functions that are inevitably coming in Canny.

So reporting does not exist in Canny right now. You will want to get as much tag, class, category, status, build, versions, use case info in place before reporting is released.

I.e. How many items are at:

- in progress / completed

- in period x where

- tag 1 and 2 were checked and where

- our customers paying more than y voted for them

Plus, using machine learning with 00s/000s of enhancements over time you might want to build a smart suggestions function, which says to a user which types of things reduce churn / lead to more sales if these are recorded on items.

“Won’t Fix” “Not a Bug”

@Andrew Rasmussen - Just connected with our new Director PM. To echo Zeb's thoughts, we want a similar "On Hold" status. "Open" currently reflects posts awaiting votes and those that have support but we're not doing. It's confusing to agents understandably. We'd like "On Hold" to reflect "Hey we've seen this but are not currently planning it. Keep voting though and we'll reconsider." Thanks.

I am looking to add additional statuses such as Near Term and Long Term to the roadmap to give users more clarity on our plans and when planned things will be delivered

We'd like a way to say: "This feature is code-complete, but it's released in an alpha-release / nightly"