You do have a point that some prioritization is helpful for an overall view of the project direction and pain points.
To me, the priority as set by the reporter is only informational in nature. We should change it if it seems exaggerated. There is a voting mechanism on JIRA that seems relevant. Also, the number of watchers. On Bugzilla the age of the bug was also a good hint, but with JIRA everything is new... --emi ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On 7 March 2018 3:31 PM, Bo Andersen <boan....@outlook.com> wrote: > I am just curious, how do you prioritize stories in JIRA? Lot of people may > create bugs, features requests and set it has high priority to get there > specific case/request solved. > > What if some one has a feature request, which not benefit the majority of > users, but only make the ide more complex to use and maintain. Are there some > main architects who decides which features needs to be implemented, or are > there some voting about the priority and/or if it's relevant? > > Thanks > > Regards Bo --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org For additional commands, e-mail: users-h...@netbeans.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
