The automation features are a bit limited. You can't specify rules
based on labels. However, the whole point of this proposal is to
replace this particular use of labels, so that wouldn't necessarily
make sense anyway.
On Fri, Jun 14, 2019 at 1:31 PM Owens, Mark wrote:
>
> I like the look of the
I like the look of the project boards based upon the ones that have been
created. I like the 'in progress' feature. It will be helpful when looking for
tickets as it will allow one to pass over issues without having to open each
issue and looking for a comment stating that someone is looking at
I'm also using a project board for tracking multiple Java 11 issues.
It's definitely useful for that case.
Nothing about this proposal (project boards for versions) precludes
the use of project boards for other purposes as well. We can have both
kinds of boards... and even personal project
I was just experimenting with a new project board for a somewhat involved
issue/enhancement.
https://github.com/apache/accumulo/projects/2
Typically we just create one issue that would spawn multiple issues. Back
in JIRA this was OK but would get confusing jumping around between all the
tickets
Accumulo Devs,
I've started to play around with the GitHub per-repository project
boards for organizing/planning some issues for 2.1.0.
https://help.github.com/en/articles/about-project-boards
I propose we use them instead of labels to track the targeted "fix
version" for our various versions.
