# Feature requests category

**URL:** <https://discourse.slicer.org/t/feature-requests-category/28>\
**Category:** Forum and website feedback\
**Created:** [April 8, 2017, 7:22pm UTC](https://discourse.slicer.org/t/feature-requests-category/28 "2017-04-08T19:22:46Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [April 8, 2017, 7:22pm UTC](https://discourse.slicer.org/t/feature-requests-category/28/1 "2017-04-08T19:22:46Z")

</div>

I suggest we add a separate category “Feature requests”. This can be used to prioritize development, collect votes on features, and discuss implementation approaches.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [April 8, 2017, 7:28pm UTC](https://discourse.slicer.org/t/feature-requests-category/28/2 "2017-04-08T19:28:46Z")

</div>

Good idea to mark feature requests, especially if we can vote for them. Can we vote?  
I think it’s also possible to define tags for each topic, so that’s an option, too (to keep the number of categories manageable).

It would be also useful to be able to mark posts about implemented new features (completed feature requests).

---

<div class="post-metadata">

**Author:** ![fedorov](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/fedorov/32/14_2.png) [@fedorov](https://discourse.slicer.org/u/fedorov)\
**Post date:** [April 8, 2017, 7:32pm UTC](https://discourse.slicer.org/t/feature-requests-category/28/3 "2017-04-08T19:32:53Z")

</div>

> [@lassoan](#):
>
> Can we vote?

We can “like”, which essentially is the same as voting. Unfortunately, we cannot sort posts by likes (or can we? maybe it’s a configuration option?).

> [@lassoan](#):
>
> I think it’s also possible to define tags for each topic, so that’s an option, too

Yes, that’s an option too, the difference is tags can be assigned by the user, and don’t need to be assigned. They could be assigned as part of triaging a topic by experienced users, but the problem is the topic can be broader than feature request. Having a dedicated category would 1) remind users that they are welcomed to submit feature requests; 2) keep topics focused on feature requests. See example of topic organization here: [http://forum.paperpile.com/c/feature-requests](http://forum.paperpile.com/c/feature-requests)

> [@lassoan](#):
>
> It would be also useful to be able to mark posts about implemented new features (completed feature requests).

We could add prefix [RESOLVED] in the title of the topic to address this?

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [April 8, 2017, 7:39pm UTC](https://discourse.slicer.org/t/feature-requests-category/28/4 "2017-04-08T19:39:42Z")

</div>

It’s possible to “close” topics. Maybe that could be usable, too.  
Not all new features are requested through the forum. Maybe a more generic name such as “New features” would cover both?

I guess we need to check out a couple of forums and learn from them.

---

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [April 8, 2017, 8:44pm UTC](https://discourse.slicer.org/t/feature-requests-category/28/5 "2017-04-08T20:44:56Z")

</div>

Here is a list of discourse instances:

> **[Discourse customers](https://www.discourse.org/customers)**
>
> We love working with our customers to host, build, and customize amazing communities.

We can also create subcategories, just for testing it I’ve added Features / Feature requests - see [https://discourse.slicer.org/categories](https://discourse.slicer.org/categories)