Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [che-dev] Issue tracking, triage, and sprint planning: is there a better option?
Thanks for the context Brian, this should have been considered earlier in the process here.
A topic that was brought up during the call that I feel didn't get enough discussion is the distinction between "moving to Jira" and "moving to the Jira instance at issues.redhat.com".
It's one thing to move to some (currently non-existent) Jira managed by the Eclipse foundation, it's another to move to a Jira that is controlled by Red Hat. While GitHub is a Microsoft product, it's a platform, and the Eclipse foundation ultimately has control of the Eclipse organization on GitHub. Moving to a Red Hat-owned Jira blurs the lines of ownership in a way I'm not entirely comfortable with -- does Red Hat support a way for external contributors to manage Red Hat Jira issues, create sprints/manage priority/etc., or are the benefits of Jira we're discussing only available to those of us with @redhat.com emails? What admin-esque privileges would the Eclipse foundation have within the Jira system?
Put another way, is moving to Jira in the way we're discussing something that another project, e.g. Theia, could also benefit from? I suspect that most of the upsides we're discussing here apply mostly to us. 

- Angel


On 2021-02-22 11:21 a.m., Brian King wrote:
Issue management/tracking/retention is considered a core aspect of an open source project, and as such, project teams are required to use resources provided by the Eclipse Foundation. 

This is captured in the project handbook, in a couple of places:
https://www.eclipse.org/projects/handbook/#project-resources-and-services <https://www.eclipse.org/projects/handbook/#project-resources-and-services>
https://www.eclipse.org/projects/handbook/#resources-issues <https://www.eclipse.org/projects/handbook/#resources-issues>
We have no current plans to support JIRA. If you want to discuss this with us, the best place to start is to open an issue in Bugzilla: https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=Infrastructure <https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=Infrastructure> 

Brian
On Wed, Feb 17, 2021 at 3:58 AM Nick Boldt <nboldt@xxxxxxxxxx <mailto:nboldt@xxxxxxxxxx>> wrote: 

    A topic raised recently in a retrospective brought to light the fact
    that there are some features missing in GH Issues, which are
    implemented in other issue trackers.

    Some of these features involve...

    * improving notifications of new issues by component (eg., Che
    server or Che dashboard) or by team/area label
    * improving triage by assigning new issues to team leads instead of
    via round-robin by non-SMEs
    * improving metadata (milestones, new&noteworthy, severity,
    priority) set on issues, to make it easier to do project/product
    releases
    * reducing manual steps involved in triage, prioritization, sprint
    planning, and handling of unplanned urgent issues
    * querying for issues closed across multiple milestones, labels,
    and/or team assignees
    * identifying resolved issues (fix is merged) vs. verified issues
    (fix exists in a built binary and has been tested to work)

    Here's a quick comparison of how some of the above concerns might be
    met by using a more feature-rich tracker:

    https://docs.google.com/document/d/1FJCqjzuQKLm-b00tmCJtvXHbOIzsqzZdlOZBz1VGayc/edit#
    <https://docs.google.com/document/d/1FJCqjzuQKLm-b00tmCJtvXHbOIzsqzZdlOZBz1VGayc/edit#>

    Maybe it's time to consider using a different tool? If the Eclipse
    Foundation can move from bugzilla and gerrit to gitlab, maybe we
    could consider continuing to use Github for pull requests and code,
    but try JIRA for its project management features? We already
    centralized all issues into a single tracker -- could we take it to
    the next level?

    What do other community members think of this idea? Any technical
    reasons why this couldn't work?

    image.png
    ;)
-- 
    Nick Boldt

    Principal Software Engineer, RHCSA

    Productization Lead :: CodeReady Workspaces

    IM: @nickboldt / @nboldt / http://nick.divbyzero.com
    <http://nick.divbyzero.com>

    <https://red.ht/sig>	
    TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>

    @ @redhatnews <https://twitter.com/redhatnews>    Red Hat
    <https://www.facebook.com/RedHatInc>
    <https://www.facebook.com/RedHatInc>


    “The Only Thing That Is Constant Is Change” - Heraclitus
    _______________________________________________
    che-dev mailing list
    che-dev@xxxxxxxxxxx <mailto:che-dev@xxxxxxxxxxx>
    To unsubscribe from this list, visit
    https://www.eclipse.org/mailman/listinfo/che-dev
    <https://www.eclipse.org/mailman/listinfo/che-dev>


_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/che-dev

Back to the top