Xiaobai, could you please tell me if an issue can be associated with a PR by assigning a responsible person? Do we only handle issues that don’t have a responsible person assigned?
The content below is generated by AI for reference only:
Summary
| Question | Answer |
|---|---|
| Can an Issue have an assignee? |  Yes, assignment is supported |
| Can an Issue be linked to a PR? | Strongly recommended and usually required |
| Must you only handle Issues without assignees? |  No, while it’s preferred to pick unassigned Issues, you can also negotiate to take over assigned ones |
We encourage you to actively contribute to the openEuler community: Find an interesting Issue → Assign it to yourself → Submit a linked PR → Complete the closed loop!
Click here to view detailed analysis and answers
Answers to Questions on Issue Assignees and PR Linking
In the openEuler community’s development workflow, Issues can have assignees, and they can absolutely be linked to Pull Requests (PRs). Handling Issues is not limited to only those without assignees.
Below is a detailed response to your questions:
Can an Issue have an assignee?
Yes. On the Gitee platform, each Issue supports assigning an “assignee” (i.e., the primary handler or responsible person).
- You can use the bot command
/assign @usernameto assign an assignee. - For example:
/assign @openeuler-ci-botassigns the current Issue to the specified user. - Assigning an assignee helps clarify task ownership and improves collaboration efficiency.
From documentation evidence:
“Currently, you can use the bot’s
/assign @***command to assist with assignment, where *** represents the Gitee ID of the person being assigned.”
—《How to assign an Issue to a responsible person?》
Can an Issue be linked to a PR?
Must be linked! The community recommends—and often requires—every PR to be associated with an Issue, forming a closed-loop tracking mechanism from “problem → fix”.
- Link an Issue to a PR by including
fixes #ISSUE_NUMBERorresolves #ISSUE_NUMBERin the PR description. - When the PR is merged, the corresponding Issue will automatically close.
- This linkage allows developers and maintainers to clearly trace how a specific issue was resolved.
From documentation evidence:
“Generally, each PR must correspond to one Issue. This ensures a clear relationship between requirements and the implemented code.”
—《Summary: How to write a good PR?》
Additionally, the knowledge graph explicitly states:
“Each PR should be linked to an Issue to establish a clear connection between the problem and its solution.”
Must you only handle Issues without assignees?
No. While it’s recommended to prioritize unassigned Issues (to avoid duplication), the following scenarios are also acceptable:
- If you are capable of resolving an Issue that already has an assignee, you can comment to communicate and request to take over after gaining approval.
- If the current assignee has not responded for a long time, community members may initiate a discussion to reassign the Issue.
- For Issues without a clear assignee, anyone can proactively claim and submit a PR.
Recommended Workflow
- Browse Issues: Go to openEuler/community-issue to view available tasks.
- Filter unassigned Issues: Prioritize Issues where “Assignee” is empty.
- Claim the Issue: Use
/assign @your-usernameto assign it to yourself. - Create a branch and fix the issue.
- Submit a PR, and in the description, include
fixes #ISSUE_NUMBER. - Wait for review and merge.
Summary
| Question | Answer |
|---|---|
| Can an Issue have an assignee? | Yes, assignment is supported |
| Can an Issue be linked to a PR? | Strongly recommended and usually required |
| Must you only handle Issues without assignees? | No, while it’s preferred to pick unassigned Issues, you can also negotiate to take over assigned ones |
We encourage you to actively contribute to the openEuler community: Find an interesting Issue → Assign it to yourself → Submit a linked PR → Complete the closed loop!