Azure / Azure/azure-sdk-tools

[JimBot] Reduced Initial Triage rule for non-product repositories

Open
#6,137 0 comments 0 reactions 0 assignees View on GitHub
GitHub Event Processor
Dominant language
C#
Stars
135
Forks
260
Avg merge
3d 1h
Merged PRs (30d)
143

Description

# Summary

For our language repositories, the [Initial Triage](https://github.com/Azure/azure-sdk-tools/blob/main/tools/github-event-processor/RULES.md#initial-issue-triage) rule is intended to help perform a fully automated initial triage by making decisions about an issue should be assigned to a member of our team, a partner team, or to the support organization.

For some of our repositories - such as [Azure SDK](https://github.com/Azure/azure-sdk), [Azure SDK Tools] (https://github.com/Azure/azure-sdk-tools), [REST API specs](https://github.com/Azure/azure-rest-api-specs) and similar, we do not want to follow the entire set of logic. Instead, we'll want to assign if and only if a member of our team is associated with the assigned label and otherwise leave it in a "Needs Team Triage" state.

# Rule Definition

## Non-Language initial issue triage

### Trigger

- Issue created

### Criteria

- Issue has no labels
- Issue has no assignee

### Actions

- Evaluate the user that created the issue:

```text
IF creator is NOT an Azure SDK team owner
IF the user is NOT a member of the Azure Org
IF the user does not have Admin or Write Collaborator permission
- Add "customer-reported" label to the issue
```

- Query AI label service for suggestions:

```text
IF labels were predicted:
- Assign returned labels to the issue

IF service label is associated with an Azure SDK team member:
IF a single team member:
- Assign team member to the issue
ELSE
- Assign a random team member from the set to the issue
- Create the following comment, mentioning other team members from the set
- "@{person1} @{person2}...${personX}"
ELSE
- Add "needs-triage" label to the issue
```

Contributor guide

Open the contributing guide

Research direction

Start with tools/github-event-processor/RULES.md and its Initial Triage section, then locate the corresponding event-processing entry point. Compare the existing behavior with the Non-Language initial issue triage definition; done means the specified labels, assignments, and comment behavior are applied for the listed non-product repositories.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp, github
Domain
tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.