github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-22 06:24:14 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

How to assign an issue to a organization member #1045

New Issue
Closed
opened 2025-11-02 03:46:28 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 03:46:28 -06:00
Owner
Copy Link

Originally created by @o3o on GitHub (Sep 7, 2017).

  • Gitea version (or commit ref): 1.1.3
  • Git version: 2.14.1
  • Operating system: Linux
  • Database (use [x]):
    • [ x] PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

I have an organization ACME with two users Alice and Bob (admin.
Bob creates a new issues but can not assign it to Alice: only "Bob" appears in the assignee list.

Is it a bug? If no how assign a issue to a organization member?
Thank you

Originally created by @o3o on GitHub (Sep 7, 2017). - Gitea version (or commit ref): 1.1.3 - Git version: 2.14.1 - Operating system: Linux - Database (use `[x]`): - [ x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description I have an organization ACME with two users Alice and Bob (admin. Bob creates a new issues but can not assign it to Alice: only "Bob" appears in the assignee list. Is it a bug? If no how assign a issue to a organization member? Thank you
GiteaMirror added the issue/staletype/bug labels 2025-11-02 03:46:28 -06:00
GiteaMirror commented 2025-11-02 03:46:29 -06:00
Author
Owner
Copy Link

@sentabi commented on GitHub (Sep 7, 2017):

  1. Create new team and add user example "CoreDeveloper", or add user to existing one.
  2. On these "CoreDeveloper" team add your user
  3. Add repository to these "CoreDeveloper" team

screenshot_2017-09-07_16-58-53

..

finally assigned able user

@sentabi commented on GitHub (Sep 7, 2017): 1. Create new team and add user example "CoreDeveloper", or add user to existing one. 2. On these "CoreDeveloper" team add your user 3. Add repository to these "CoreDeveloper" team ![screenshot_2017-09-07_16-58-53](https://user-images.githubusercontent.com/203196/30157964-e6ebd826-93ed-11e7-8924-16f4346486b0.png) .. ![finally assigned able user](https://user-images.githubusercontent.com/203196/30158176-943c23e6-93ee-11e7-8b63-49acbd361107.png)
GiteaMirror commented 2025-11-02 03:46:29 -06:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Feb 6, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 6, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.
GiteaMirror commented 2025-11-02 03:46:29 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Feb 7, 2019):

I think this is not an issue any more.

@lunny commented on GitHub (Feb 7, 2019): I think this is not an issue any more.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/stale type/bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#1045
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?