Skip to content

Bug: Can't set assignee after removing initial assignee #7318

Open

Description

@haiodo

Summary

Reported by a user in the community: After creating and assigning a user, when the initial assignee is removed they can’t set another assignee other than themself (see screen recording attached)

Steps to reproduce:

  • create task and assign to user A
  • in the task details remove user A as the assignee
  • try to add a new user to assignee but not able to
  • the only user I can assign to this task is now myself

Actual Result

User can only add themself as an assignee after issue has been created.

Expected Result

User should be able to add any project member as the assignee for the issue.

Huly®: UBERF-8522

Activity

  1. self-assigned this
    on Dec 8, 2024
  2. haiodo commented on Dec 8, 2024

    @haiodo
    ContributorAuthor

    Github project allow to assign only authenticated to same repository persons.

  3. haiodo commented on Dec 8, 2024

    @haiodo
    ContributorAuthor

    Othervise it will not be abble to sync to github, probable we need to disable this logic in case issue is not connected to repository.

  4. AbigailDawson commented on Dec 8, 2024

    @AbigailDawson
    Contributor

    Ok will let the user know, thanks!

  5. AbigailDawson commented on Dec 8, 2024

    @AbigailDawson
    Contributor

    So it seems you can assign a user when the issue is created, you just can’t re-assign after it was already created, is that expected?

  6. haiodo commented on Dec 8, 2024

    @haiodo
    ContributorAuthor

    It is just a bug I suppose.

  7. haiodo commented on Dec 8, 2024

    @haiodo
    ContributorAuthor

    Create/Assign should be same, we should be able to choose only persons from associated github.

  8. MichaelUray commented on Oct 18, 2026

    @MichaelUray
    Contributor

    The GitHub-integration rule that limited issue assignees to linked GitHub users, and blocked changing or unsetting the assignee, has been removed. Any person can now be assigned or re-assigned after the issue is created. This was done in #8179. This looks resolved, so the issue could be closed.

  9. MichaelUray commented on Oct 20, 2026

    @MichaelUray
    Contributor

    @haiodo — based on the check described above, this looks resolved in the current code. Could you please close this issue if you agree? If you think it is not fixed yet, please describe what still goes wrong (steps, expected vs. actual behaviour), so it can be looked at again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions