Problem: labels are not automatically assigned to Application

[zolotokrylin]

Problem

When a new application is submitted, the candidates need to manually specify the role in the title. This creates inconsistency and makes application filtering harder.

Solution

To automatically assign labels to issues created from this template, you need to add a labels field to your issue template.

Auto-assign Fixed Label

Add a labels field at the top level of the template. These labels will be automatically assigned:

...
labels: ["job-application"]  # These are auto-assigned
...

## Let Users Select Labels
Unfortunately, **GitHub doesn't natively support a dropdown field in issue templates that auto-assigns labels**. However, you can work around this by:

1. **Adding a dropdown field** for users to select their department/team:
```yaml
  - type: dropdown
    id: department
    attributes:
      label: "Department"
      description: "Select your department (this helps with routing)"
      options:
        - Engineering
        - Marketing
        - Design
        - Sales & Business Dev
    validations:
      required: true

2. Then use a GitHub Action to automatically assign labels based on the selected value. Extend existing workflow (.github/workflows/comment-bot.yml):

# This is pseudo code

name: Auto-label Job Applications
on:
  issues:
    types: [opened]

jobs:
  label:
    runs-on: ubuntu-latest
    if: contains(github.event.issue.labels.*.name, 'job-application')
    steps:
      - uses: actions/github-script@v7
        with:
          script: |
            const body = context.payload.issue.body;
            const departmentMatch = body.match(/### Department\n\n(.*?)(?:\n|$)/);
            if (departmentMatch) {
              const department = departmentMatch[1].trim();
              github.rest.issues.addLabels({
                owner: context.repo.owner,
                repo: context.repo.repo,
                issue_number: context.issue.number,
                labels: [department.toLowerCase().replace(/\s+/g, '-')]
              });
            }

[github-actions]

🎉 Thank you for your application!

✅ What's next?

1. Familiarize yourself with our Guidelines;
2. Execute a trial by merging two PRs:
   • 1st PR: submit your profile to our simple JSON file,
   • 2nd PR: complete a test to prove your skill (will be provided by our team member),
3. Follow our socials and consider tweeting about us:
   • Official Holdex X
   • Holdex CEO
   • LinkedIn

How to Submit Your Profile

1. Fork this repository
2. Add your profile in the profile-submission.json file:

   {
     "github_handle": "your_github_username",
     "full_name": "Your Name",
     "github_trial_issue_link": "https://github.com/holdex/trial/issues/your_issue_number"
   }

3. Create a Pull Request (PR), attach it to this issue and wait for the review.

Questions?

If you have any questions, feel free to ask them directly in this issue 😉

[forvy]

I would prefer the hybrid approach:

• Keep a fixed job-application label auto-assigned at the template level for consistent filtering.

• Add a required dropdown field for department.

• Use a GitHub Action to dynamically assign the department label based on the selected value.

This keeps filtering consistent while also allowing structured routing without relying on users to manually edit titles.

The Action-based approach scales better if departments change or if we want to extend routing logic later (e.g., assigning reviewers automatically).

[zolotokrylin]

@forvy, OK.