search

codelerity / netbeans-issues-test

Testing issue templates for Apache NetBeans
Apache License 2.0
0 stars 0 forks source link

Test issue #1

Open neilcsmith-net opened 2 years ago

neilcsmith-net commented 2 years ago

Apache NetBeans version

Latest release candidate

What happened

Exceptions are thrown when coding Java on JDK 8.

How to reproduce

Press enter on code new line.

Did this work correctly in an earlier version?

Operating System

Ubuntu 20.04 amd 64

JDK

Azul Zulu 17 amd64

Apache NetBeans packaging

Own source build

Anything else

Nothing else to report

Code of Conduct

ebresie commented 2 years ago

Is it possible on creation to automatically add the "needs:triage"? If so then it would allow to filter on items needing triage to be performed.

That said, in theory on JIRA all open (not closed) could have a "triage" label added, then filtered by items needing triage, then make a concerted effort to have triage all of them and determine (1) is this still a bug or OBE, (2) is there a fix that resolves this and if so link it up; this could be an "after the fact" sort of activity. (3) is this a duplicate of something else, and on completion, remove the triage label.

ebresie commented 2 years ago

Is it possible to have additional "quality or process checklists" type items (similar to the above "This used to work!") to be added to the template to suppport for consistent handling?

Not quite sure of the specifics yet so just thosing some ideas around like: (1) Is the issue able to be reproduced (yes/no) (2) Is a fix been completed / a PR been created (3) Has a unit test been created or update to test issue? (4) Is this a security issue?

ebresie commented 2 years ago

Is there any other ways to consider for grouping things? I think it was suggested to have things like "Gradle" and other items?

At one point I thought linking it to a "netcat tribe" may be one way of doing so. This would then allow the "netcat" group to help act as a quality role and focus to the applicable Subject Matter Experts of the given type/tribe.

So in otherwords, if a "triage" label is present and the "grouping" tag was present, it could be filtered by the group to see all items requring triage by the group.

neilcsmith-net commented 2 years ago

@ebresie automatic labelling already happens. 2 and 4 (and probably 3) of your list should never result in an issue. Try working through an issue from the beginning - test here or port an important JIRA ticket to NetBeans. You'll see what I mean.

ebresie commented 2 years ago

Started writting then lost what I was writing so will try again...

@neilcsmith-net sorry about that, I noticed after posting the autolabeling was happening.

I have seen usages of issue tracking, where for the issue some "checklists" are available to help make sure somethings not missed and/or to show progress. Something like this ( https://marketplace.atlassian.com/apps/1211562/checklist-for-jira?tab=overview&hosting=cloud )

I was trying to imply for example, while working the issue if a fix is available, then check it off; if it is able to be reproduced then check yes/if not then either hasn't been identified or is not reproducible and should probably be rejected; when a unit test has been updated/created then check it to ensure test coverage for the issue exists (I suppose it's not necessarily needed to be updated but maybe identify which unit test this may be seen as part of).

Items like security could be a check box but in hind site, maybe this is better as a label/area/grouping/category (whatever you want to call it) type field (i.e. label:security).

Was the suggestion to raise a real issue here and work it through?

Like maybe https://issues.apache.org/jira/browse/NETBEANS-189 (and/or related https://issues.apache.org/jira/browse/NETBEANS-5831 ) which is associated with PR https://github.com/apache/netbeans/pull/3074 ?