Let us customize the names of the statuses. Specifically I want to change "Under Review" to "Researching" or "Scoping". "Under Review" sounds like the post is under review and might get deleted
“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 just like on other product roadmaps - https://trello.com/b/ZnTQyumQ/slack-platform-roadmap-for-developers https://www.prodpad.com/about-us/our-roadmap/
Thanks @Nicholas Merican! Sounds like this post is more specific for what you're looking for: https://feedback.canny.io/feature-requests/p/status-updates-dates
We'd like a way to say: "This feature is code-complete, but it's released in an alpha-release / nightly"
@Norbert de Langen: Hey Norbert, any reason why "In Progress" doesn't work for you?
@Sarah Hum:
I want to signal to users their requested feature is available for testing.
@Norbert de Langen: I see. We try to be very careful with which statuses we choose to promote to the main roadmap. In your case, I'd recommend just leaving a comment saying that the feature is ready for testing. Everyone who voted will get a notification.
We really need a way to say "Not planned" (ie. not going to do right now).
@Zeb: Hey Zeb!
For posts that we don't plan on doing right now, we just leave them open. This lets us measure interest, in case we want to build the feature in the future.
For posts that we never plan on doing, we mark them as "Closed". This communicates you won't be building the feature, and gives you an opportunity to explain why.
Does this for you, or do you still feel like a "Not Planned" status would solve some problems for you?
@Andrew Rasmussen: Hey Andrew! Hope you guys are living the dream traveling still!
We could use "Closed" but it just doesn't really categorize it well in my opinion. Also we would still like to have it visible to users so they can add feedback, while being transparent in that feature is not planned.
We currently used "closed" for things like user error, or things that already exist. We just have tons of requests and it's hard to sift through them all, but I think a "not planned" status would help us in that.
But I hear your reasoning completely and I understand why you want them to remain the same and simple, we struggle with this too haha and I'm always the one that wants to keep them the required statuses static: https://feedback.clickup.com/feature-requests/p/change-default-required-statuses
@Zeb: I definitely see the value in "Not Planned", since I often use "Closed" for the same thing you mention: invalid tasks, errors, or things that already exist.
I want this,too!
I like the simplicity of fixed statuses by Canny however, custom statuses would be great. For example, we would like to communicate to our users that a feature is being tested / QC/QA before it goes to complete just so users are aware of the stages / process we take.
Hey Michael, thanks for the feedback! To be 100% honest, we aren't super happy with "Under Review" either. We considered many options, and it seemed like the least worst one.
It was important to us that the status was an actual status: "This post is X". "This post is Under Review/Planned/etc" works, but "This post is Researching/Scoping" doesn't.
We also considered "Under Consideration" but felt it was too long.
If you have other ideas that fit the format above, we'd love to hear them!
@Andrew Rasmussen: "Considering" or "Reviewing" ?
@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.