I suppose you could look at the small green symbol on the left of the issue title, but I find a label more visible.
Having a feature request label will also allow easy filtering on that issue category. On Tue, Feb 26, 2019 at 2:10 PM Jonathan Wei <jon...@apache.org> wrote: > If I'm in a view where I see both feature request issues and pull > requests, I think it's nice to be able to tell right away what the issue > type is. > > If someone creates a feature request like "Add <feature-name>", that title > also works as a pull request title, I see no reason to have that ambiguity. > > On Tue, Feb 26, 2019 at 1:32 PM Roman Leventov <leventov...@gmail.com> > wrote: > >> Code contributions are PRs, they could be filtered via is:pr (or is:issue >> if you want the opposite) in issue search on Github, isn't that enough? >> >> On Mon, 25 Feb 2019 at 23:03, Jonathan Wei <jon...@apache.org> wrote: >> >> > "Problem Report" sounds fine to me, maybe we could have an automatically >> > assigned "Problem Report" tag and a separate "Bug" tag. In general I >> want >> > to have [TAG] or github labels on issues for easy identification. >> > >> > For the feature requests, I think they should be tagged automatically >> for >> > easy visibility, and you make a fair point re: "Wish list". I would >> suggest >> > "Feature/Change Request" as the label text (or some other word with >> similar >> > meaning as "request" if that's too similar to "pull request"), to make >> it >> > clear that those issues are not code contributions. >> > >> > Thanks, >> > Jon >> > >> > On Mon, Feb 25, 2019 at 2:24 PM Roman Leventov <leven...@apache.org> >> > wrote: >> > >> > > I suggest renaming "Bug Report" to "Problem Report" (and not >> > automatically >> > > assign a "bug" tag) because sometimes the problems that are reported >> by >> > > users are not the result of bugs in Druid, but, for example, misuse, >> > > misconfiguration, use of old Druid version, etc. Druid committer >> assigns >> > a >> > > "bug" tag when he reads the issue and verifies that it's probably >> caused >> > by >> > > a bug. >> > > >> > > I also suggest removing "Wish list" tag and not assign it in >> > > "Feature/Change request" template automatically. Or rename it to >> > objective >> > > "Feature", or "Feature/Change". "Wish list" is subjunctive - who >> wishes >> > > that change? The author? The community? >> > > >> > >> >
