When adding a link in JIRA on a ticket to the PR  it seems to link up
there.  Is the concern this is a manual step instead of more automated?

Is the concern the # of JIRA tickets not going down?  If it switched to
GitHub would that change really?  Is it really just people dedicated to
management of the tickets?  If so (think I mentioned this before but) is
some form if change control needed? Maybe a CCB mailing list is needed to
focus on this sort of thing?  JIRA provides dashboards and burn down
reports which can help monitor things as well (
https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333642)

Not sure if this helps any or if this is already in use in some way but
JIRA has integration with GitHub.

https://support.atlassian.com/jira-cloud-administration/docs/integrate-with-github/

Atlassian suite offers bitbucket, review, CI, and other related tool sets.
Is this maybe partly an issue that those are not in use on the project?
Assume having those involved would possibly be an additional cost for
usage.

Seems like some of this is some features are being used in JIRA and others
in GitHub which are in many ways competing products

Eric

On Fri, Sep 24, 2021 at 7:16 AM Christian Lenz <[email protected]>
wrote:

> I see a big Benefit out of it also to have everything in one application
> (Pipeline, Discussions, Issues, etc.). As the other one, on the other
> mailinglist already mentioned:
>
>
> That was such an amazing improvement in the overall workflow and
> contributor's engagement
>
>
> Cheers
>
> Chris
>
>
> Von: Eric Barboni
> Gesendet: Freitag, 24. September 2021 13:29
> An: [email protected]
> Betreff: RE: Apache JIRA vs GitHub issues / discussions
>
> I don't know. Would be happy with both. I suspect, we will still have lots
> of opened untackled issue on git issue too.
>
> Would be good to hear from major our major contributor.
>
> Best Regards
> Eric
>
> -----Message d'origine-----
> De : John Mc <[email protected]>
> Envoyé : jeudi 23 septembre 2021 22:42
> À : dev <[email protected]>
> Objet : Re: Apache JIRA vs GitHub issues / discussions
>
> Interesting point,
>
> JIRA seems very decoupled from everything else at the moment.  We have a
> lot of open tickets there ~3000 and we're not doing a great job keeping an
> eye on it.
>
> it might allow people to raise bugs more freely as more users would have
> GH accounts then Apache JIRA accounts so it make it easier for users to
> submit bugs..
>
> Regards
>
> John
>
> On Thu, 23 Sept 2021 at 15:43, Neil C Smith <[email protected]> wrote:
>
> > Hi,
> >
> > I've long felt that our use of JIRA and poor integration with the PR
> > process, etc. is more of a hindrance than a help, particularly during
> > releases.  This email just popped up on users@infra (needs sign in)
> > about Apache Airflow's switch a couple of years back.  Found it very
> > interesting - food for thought?
> >
> >
> > https://lists.apache.org/thread.html/r65aae462b9f26454adaf9e5854dda06b
> > 2acd10273cb1b34b3e6b1227%40%3Cusers.infra.apache.org%3E
> >
> > Best wishes,
> >
> > Neil
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
> --
Eric Bresie
[email protected]

Reply via email to