Add issue type to existing issues in all repos

[hannes-ucsc]

Perform the following actions for each of our active repositories, starting with Azul:

1. Apply the issue type Bug to all untyped issues labeled bug
2. Apply the issue type Task to all untyped issues labeled task
3. Apply the issue type Feature to all untyped issues labeled enh
4. Review the remaining untyped issues and confer with lead about next steps
5. Delete the labels bug task and enh

Our active repositories are listed here. Please also include HumanCellAtlas/dcp2.

Synchronize the labels from Azul to each of the above repositories.

A filter like is:issue label:bug no:type might come in handy.

[edit: @hannes-ucsc} Also requires two PRs: https://github.com//issues/6875#issuecomment-2651624715

[achave11-ucsc]

Confer with lead on the untyped issues in the following repos:

• HumanCellAtlas/dcp2
• DataBiosphere/azul-private
• DataBiosphere/data-browser
• DataBiosphere/data-portal
• DataBiosphere/azul

[achave11-ucsc]

@hannes-ucsc: "I accidentally included portal and browser in the description. We don't want to touch this repositories because most of the issues in them are not for us."

[achave11-ucsc]

All azul:labels are synced with:

• azul-chalice
• azul-docker-elasticsearch
• azul-github-labeler-action
• azul-private
• HumanCellAtlas/dcp2

[hannes-ucsc]

#6875 (comment)

The errors directly above are caused by the removal of certain labels, task among them, as part of #6889. To address this, that issue requires a first, partial PR that removes these labels from the issue templates (so that issues are created on schedule again) and another final PR to update the scheduled issue creation workflow to set the issue type based on information in the template.

[hannes-ucsc]

For partial demo, visit all repos and show that the labels mentioned in the description are gone and that labels are in sync with Azul. Show that at least one scheduled issue has the labels specified in the template. The latter depends on #6875 being fixed, hence demo blocked.

[edit: @hannes-ucsc] … only for scheduled issues in azul-private so demo can move forward, with a scheduled issue for the azul repo. The blocking relationship is actually the other way around.

[achave11-ucsc]

Assignee to file second, final PR.

[achave11-ucsc]

@hannes-ucsc: "It doesn't appear to be any API support for setting the issue type. Assignee to monitor GitHub documentation and re-triage once API support is available and documented."