# Milestones / Status as subcategories added for features and bugs categories **URL:** \ **Category:** Feature\ **Created:** [22 Dezembro , 2014 04:46 UTC](https://meta.discourse.org/t/milestones-status-as-subcategories-added-for-features-and-bugs-categories/23328 "2014-12-22T04:46:20Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![gingerman](https://avatars.discourse-cdn.com/v4/letter/g/47e85d/32.png) [@gingerman](https://meta.discourse.org/u/gingerman)\ **Post date:** [22 Dezembro , 2014 04:46 UTC](https://meta.discourse.org/t/milestones-status-as-subcategories-added-for-features-and-bugs-categories/23328/1 "2014-12-22T04:46:20Z")
As a newbie joining the discourse community, it is extremely difficult to understand the status of features and bugs reported. If the topic is closed, may be we can assume it is implemented. Why can’t we add sub-categories under features / bugs with versions like 1.2, 1.3, 2.0, later and add them to relevant topics. Some project teams maintain them in github / trello…we can easily define that in sub-categories. It will really help anyone to understand the priorities of the discourse team before pushing them for features. In the present scenario, unless a community member tells about the priorities or link multiple roadmap topics a newbie has no clue. --- _[View the full topic](https://meta.discourse.org/t/milestones-status-as-subcategories-added-for-features-and-bugs-categories/23328)._