Central GA4GH Ticketing

[MKonopko]

Per M Haendel:

a place to put requests such as these. It would be terrific if there was a more coordinated suite of GitHub repos and a central ticketing/work tracking system across them for GA4GH. Please let us know if you want help or advice in setting up such a thing, we are happy to contribute.

[jb-adams]

@MKonopko @mellybelly one way to track incoming requests would be through the GA4GH Organization-level Project boards on Github (link). We currently have boards for specific projects, but could potentially add a board for TASC and/or general GA4GH work.

[mellybelly]

I love the board :-)

[rishidev]

Defer until technical team is in place 2021 if this is feasible.

[uniqueg]

I just wanted to bump this and say that I 100% agree that GA4GH should offer a centralized entry point for raising issues/tickets. In my opinion, it would be crucially important especially for newcomers and one-off or casual contributors , but also for regular contributors (as it is, I only found out today that in fact there is a TASC repo and project board).

I could imagine a publicly available open (i.e., no auth) service with a form that people can fill in issues. It could provide checklists for work streams and individual specs/standards that submitters could optionally make use of. This info could then be used to automatically create issues, via the GitHub API, in the appropriate repos for further manual triaging by WS and API/standard champions. Issues that do not have any info to allow us to identify a suitable repository would end up in some dummy repo and would need to be manually triaged and transferred to an appropriate place.

Ideally, the service could also make use of the GitHub API to list all available issues for people to search through before filing an issue (or, ideally, suggest related issues) to avoid duplicates. But that may be a second step. Although perhaps the whole service could be a Google Summer of Code project.

[uniqueg]

Or JIRA: https://www.atlassian.com/licensing/purchase-licensing#pricing-discounts

[mellybelly]

I couldn't agree more about the importance of a one-stop shop for anyone to submit a ticket (and have it delivered to the correct team) as well as the inventory of standards and their associated repos/ticketing systems (i.e. #7). Overall, we continue to have very many different places to work, making coordination across them challenging.

[larrybabb]

Can we define whether or not there's a well defined structure to the "products" or "resources" that can have tickets associated so that this can be modeled after that? For example, should we do this for products only or do other "resources" need to have a place for folks to submit "tickets"? Do we also need to define some type of minimal communication policy on how the individual "ticketable" ga4gh "things" respond to those tickets (e.g. some response within X days to acknowledge receipt, an assigned individual on the ga4gh side to address the ticket, etc...)

[ajhpage]

**Recommendation: move this a subtask of the Github Overhaul issue #54: **

Pieces of this are already in progress:

• coordinated suite of github repos: completely solved when github overhaul is complete >> in progress
• central ticketing system across them: central repo managed by ops which would triage and send to the proper team, a piece of work built out in, submit things into a single place >> set this up and have GA4GH ops lead it
• project tracking: one place to see all things being worked on across ga4gh, infrastructure is there but needs to be a sub-issue to the github overhaul issue, the org level project. not sure how useful this is, showing off what we're doing could be useful. from a WS process level may not be as necessary.

---

Minutes from GA4GH Connect conversation:
this will be addressed by github overhaul, cetnralizing github management in tech team, which will allow a way for people to raise tickets, which we don't currently have; it will exist soon, as TT migrates away from Jira into managing all work on github, more transparency. can use gitboards for project management inside github. need to manage projects where we're doing the work. cetnral ticketing will be solved when the migration is complete. Make sure this issue is fed intot he requirements gathering. link this as a dpendency for that ticket. This ticket is no longer relevant as a standalone ticket. this is a subissue of the github repo reorg. in progress.

could be a help desk where the issues are sent appropriate. the non technical peices of this, (eg general queries). Aspects of this have been solved in the launch of the new website. There's an ongoing piece of work to the tech team surfacing their work to allow people to create issues.

It would also be nice to have a central place

use github issues as the help desk, and they could be farmed out to the right places

is this going to solve or address the problem raised -- GA4GH operations should be able to manage this.

LLM on the gA4GH website?!

Sasha aims to create a high level roadmap board in TT repo so everyone can see the strategic pieces of work they are doing, if we can get that working, to get status of how things are going and where there is work to be done.