Outcome Overview

How should we use both JIRA and GitHub — or just JIRA?
We will define a clear, simple, and team-aligned process for managing tasks across JIRA (required) and GitHub Issues (optional and under review).

• JIRA will remain mandatory for tracking RedHat BU work — including internal planning, delivery, and strategic initiatives. It is our system of record and must be used.

• GitHub Issues, currently used by RedHatters outside the team, upstream/community contributors, and some team members, is under evaluation. While GitHub is often more accessible and familiar for these audiences, we may choose to:
  • Continue using it in a more structured way, with clear links to Jira
  • Limit its use to specific contributor types or workflows
  • Or phase it out entirely, especially now that our JIRA instance is publicly accessible

The goal of this outcome is to:

• Reduce friction for both internal and external collaborators
• Ensure priorities and ownership are clear across all platforms
• Document and adopt a workflow that supports open collaboration while preserving RedHat BU structure and visibility

Success Criteria

• There is a clear, shared definition of how we work with both JIRA and GitHub Issues.
• A simple, written guidance document is created, shared, and accessible to all contributors.
• Priorities are visible and understandable for RedHat BU, the internal team, and external collaborators (RedHatters, IBMers, upstream/community).
• A standard process exists for identifying and linking high-priority tasks between GitHub and JIRA (or migrating them when needed).
• The agreed workflow is understood and adopted by the team, with no recurring confusion on where or how to track work.

Expected Results (what, how, when)

The Team Feels Confident and Clear

• What: Everyone knows where to work, how to contribute, and how to communicate what matters most — internally and externally.

• How: Fewer repeated questions or confusion in team discussions.
• When: This result is considered achieved when the workflow, tools, process, and standards are agreed upon, documented, and shared — and actively used by the team in real work