Problem

Advanced issues are higher risk and require extensive knowledge of the codebase

We should ensure a human triage/committer/maintainer cannot incorrectly assign a developer that wants to work on an advanced issue, that does not have the basic pre-requisites

Solution

Create a workflow, similar to
.github/scripts/check_assignment_limit.sh
.github/workflows/bot-assignment-check.yml

When an issue is labelled advanced, ensure that a user cannot become assigned to it unless:

• they have completed at least one prior 'Good First Issue' issue
• and at least one prior 'intermediate' issue

maintainer, committer or triage should not face this limitation, in the rare case we have a historical committer or maintainer that has not completed issues with the new labels
hiero-ledger/hiero-sdk-python-triage
hiero-ledger/hiero-sdk-python-committers
hiero-ledger/hiero-sdk-python-maintainers

It should respond with a friendly message something along the lines of

• cannot assign you
• this advanced issue requires completing GFI and intermediate issues first
• you have completed xGFI and xintermediate issues

Will require a lot of testing to get this right on a fork hence why is advanced
Depending on the number of API calls this will use, you may also have to ensure it is economical with API

Alternatives

Open to suggestions