Labeling issues using either labels or components sounds good to me!
If we plan to use the code components as labels @bgchun suggested, let's use JIRA components. But if we plan to add other labels that are not code components in the future (ex. for beginners, bug fix, refactor), let's use labels :) I would love to open up the floor for further discussion. Best, Joo Yeon On Tue, Jun 5, 2018 at 3:21 PM, John Yang <[email protected]> wrote: > Hi, > > > How about using JIRA components? > > It appears that we can use any string for a label, and clicking on a label > by default shows all issues of all JIRA projects that have the label. > On the other hand, components provide a fixed number of options, and nicely > show our issues by component. > > REEF and Spark are also using components. > > - REEF: > https://issues.apache.org/jira/projects/REEF?selectedItem=com.atlassian. > jira.jira-projects-plugin:components-page > - Spark: > https://issues.apache.org/jira/projects/SPARK?selectedItem=com.atlassian. > jira.jira-projects-plugin:components-page > > I'd be happy to set up components for the community. :) > > > Thanks, > John > > > On Sun, Mar 4, 2018 at 4:15 PM, Sanha Lee <[email protected]> wrote: > > > +1 > > > > Thanks for the suggestion! > > I'll update existing issues with these labels. > > > > Sincerely, > > Sanha > > > > 2018-03-04 15:33 GMT+09:00 Jean-Baptiste Onofré <[email protected]>: > > > > > +1 > > > > > > it sounds good to me. > > > > > > Thanks ! > > > > > > Regards > > > JB > > > > > > On 03/04/2018 07:31 AM, Byung-Gon Chun wrote: > > > > Hi, > > > > > > > > Let's use labels when we add JIRA issues. > > > > How about the following labels to start with? > > > > compiler > > > > runtime > > > > client > > > > common > > > > conf > > > > tests > > > > examples > > > > > > > > Cheers, > > > > Gon > > > > > > > > > > -- > > > Jean-Baptiste Onofré > > > [email protected] > > > http://blog.nanthrax.net > > > Talend - http://www.talend.com > > > > > >
