Creating issues to Add Missing Labels to Issue Templates

[jdingeman]

Dependencies

• Update labels: Issue Template: blank-issue-form-with-dependency #4491
• Update labels: Issue Template: blank-issue-form-with-no-dependency #4485
• Update labels: Issue Template: feasibility-issue-template #4490
• Update labels: Issue Template: gha-issue-template #4475
• Update labels: Issue Template: Mobile_responsiveness #4483
• Update labels: Issue Template: alt-text-audit--dev #4477
• Update labels: communities-of-practice-information-updates #4486
• Edit System Audit: text  #4482
• Update labels: Issue Template: pre-work-template---design #4480
• Update labels: Issue Template: pre-work-template---ux #4484
• Update labels: Issue Template: pre-work-template--dev #4478
• Update labels: Issue Template: suggest-a-feature-or-new-content-for-hackforla-org #4481
• Update labels: Issue Template: wiki--research-plan-review----replace-with-name-of-page- #4488
• Update labels: Issue Template: emergent-request #4502
• Update labels: Issue Template: suggest-an-external-resource #4476
• Update labels: Issue Template: project-profile-card-review-and-update #4489
• Update labels: Issue Template: blank-issue-template #4503
• Update labels: Issue Template: suggest-a-guide #4487
• Update labels: Issue Template: creating-a-yml-file-for-a-sdg #4479

Overview

Developers have noticed that the GitHub bot will remove a label if a dev who creates an issue adds a label immediately after clicking "Submit new issue." We need to add the labels from the Missing series to the Issue Templates to prevent the GitHub bot from removing the labels, since the labels will already be set.

Action Items

• This issue should only be assigned to a lead
• In the Dependency section of this issue, click on each item to create the issue with the correct name (one at a time)
  • Paste the body template (1 or 2) from below into the issue and customize from the HLFA site: Audit: New Issue Template labels spreadsheet (see resources)
    • [ISSUE TEMPLATE YML] will be replaced with the corresponding issue template name
    • [INSERT CONTENT FROM SHEET] will be replaced with the current line and new line values in the spreadsheet
  • Add the labels good first issue size: 0.5pt role: front end role: back end/devOps, Feature: Board/GitHub Maintenance, ready for dev lead
• Once all necessary issues have been created
  • remove the subheadings that say #### Issues that use template 1 and #### Issues that use template 2
  • add a dependency label
  • move this issue to the Ice Box column
• If all the dependency issues are closed, remove the dependency label, move this issue from the Ice Box to the In Progress column, and close this issue.

Resources/Instructions

• HLFA site: Audit: New Issue Template labels
• Issue templates
• How to create issues
• ER associated with this issue: ER: github-actions bot removing Draft label #3758

Body Template 1

### Prerequisite
1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our [Getting Started page](https://www.hackforla.org/getting-started) and attend an onboarding session.
2. Please make sure you have read our **[Hack for LA Contributing Guide](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md)** before you claim/start working on an issue.
### Overview
As developers, we need to add the labels from the [Missing series](https://github.com/hackforla/website/wiki/How-to-read-and-interpret-labels#missing-series) so that we can avoid the GitHub bot taking off the labels when devs add them to issues.
### Action Items
- [ ] Navigate to `.github/ISSUE_TEMPLATE/[ ISSUE TEMPLATE YML ]`
- [ ] Add the following line under the description field
   ```
   labels: ['role missing', 'Complexity: Missing', 'Feature Missing', 'size: missing','Draft']
   ```
**For PM, Merge Team, or Tech Lead**
- [ ] Once the pull request associated with this issue is approved and merged, please update and edit epic #4307 by
  - [ ] Checking off the dependency for this issue
  - [ ] If all dependencies are checked off, please move issue to the New Issue Approval column and remove the Dependency label

#### File and Code links you will need to work on this issue
- Directory to find the page in once you have it in your IDE: `.github/ISSUE_TEMPLATE/[ ISSUE TEMPLATE YML ]`
- This issue is part of epic #4307

Body Template 2

### Prerequisite
1. Be a member of Hack for LA. (There are no fees to join.) If you have not joined yet, please follow the steps on our [Getting Started page](https://www.hackforla.org/getting-started) and attend an onboarding session.
2. Please make sure you have read our **[Hack for LA Contributing Guide](https://github.com/hackforla/website/blob/gh-pages/CONTRIBUTING.md)** before you claim/start working on an issue.
### Overview
As developers, we need to add the labels from the [Missing series](https://github.com/hackforla/website/wiki/How-to-read-and-interpret-labels#missing-series) so that we can avoid the GitHub bot taking off the labels when devs add them to issues.
### Action Items
- [ ] Navigate to `.github/ISSUE_TEMPLATE/[ ISSUE TEMPLATE YML ]`
- [ ] Replace the following line
   ```
   [INSERT CONTENT FROM SHEET]
   ```
   with
   ```
   [INSERT CONTENT FROM SHEET]
   ```

**For PM, Merge Team, or Tech Lead**
- [ ] Once the pull request associated with this issue is approved and merged, please update and edit epic #4307 by
  - [ ] Checking off the dependency for this issue
  - [ ] If all dependencies are checked off, please move issue to the New Issue Approval column and remove the Dependency label

#### File and Code links you will need to work on this issue
- Directory to find the page in once you have it in your IDE: `.github/ISSUE_TEMPLATE/[ ISSUE TEMPLATE YML ]`
- This issue is part of epic #4307

[github-actions]

Hi @jdingeman.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:
Complexity, Role, Feature

NOTE: Please ignore the adding proper labels comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels