If there is an inherent issue with the existing site, it is classified as a bug/issue. If it’s new functionality that is requested to be added in the future to make YEN better, it is classified as a
Feature Request. There are times however that things may blur the line and the judgement of the core team will be used.
Currently there are three priorities of issues:
High - Bugs that are preventing users from basic core functions (ex. transactions, posts)
Normal - Bugs that are distracting to but not preventing basic core functions
Low - Modifications to make existing features better
There is one bucket for all feature requests to hold all submissions. The priority of feature requests is evaluated at the beginning of each sprint against a larger picture of the future direction for the community and site. Depending on the number of requests put in via the @yensupport tag and feedback from user interviews, the priority of future features can be shifted.