+1 for using github
I have used both - I am more failure with github then Jira capabilities.
Jira for me was very slooooow.
So if there is a Jira PRO on the team and they can automate Github PR/Issue
tracking and syncing/closing into Jira that would be the way to go.
The benefit is that disjoint tools are not in the way of project success.
The Key features of Github that make it the right *integrated* choice are:
1) It automatically crosslink issue and pr and can close issues on PR
coming in.
2) Cross repo PR/ISSUES are already supported with inline mark up [SEE
SISTER {PR|ISSUE}] (url)
3) Git hub ass project board and supports kanban boards[1]
4) As Alin mentioned Template driven USER first encounter triage
4) A single login/location for complete lifecycle.
David
[1]https://www.atlassian.com/agile/kanban/boards
-----Original Message-----
From: Alin Jerpelea [mailto:jerpe...@gmail.com]
Sent: Monday, December 30, 2019 1:23 AM
To: dev@nuttx.apache.org
Subject: Re: Issue Reporting
for another bug tracker we use github and all issued are created on a
template.
This template can start with the following title "git name - board /
component - version - issue".
Such layout eases the sorting and people can easy spot if there is
something similar to theyr issue.
On Mon, Dec 30, 2019, 04:17 Gregory Nutt <spudan...@gmail.com> wrote:
>
> > I like this. I prefer that we use Apache's Jira for several reasons,
> > especially in light of the integration that Brennan describes.
> If we do go with Jira, we should transfer all of the Bitbucket nuttx/
> and apps/ issues to Jira along with the content of the NuttX TODO list.
>
