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

List tickets assigned to a person #8309

New Issue
Closed
opened 2025-11-02 08:01:53 -06:00 by GiteaMirror · 3 comments
GiteaMirror commented 2025-11-02 08:01:53 -06:00
Owner
Copy Link

Originally created by @laurivosandi on GitHub (Jan 3, 2022).

Feature Description

Organization owner should be able to view tickets assigned to a organization member

Currently it seems this is not implemented anywhere? Looks like trivial change as this would be pretty much same as "Assigned to you"

Screenshots

No response

Originally created by @laurivosandi on GitHub (Jan 3, 2022). ### Feature Description Organization owner should be able to view tickets assigned to a organization member Currently it seems this is not implemented anywhere? Looks like trivial change as this would be pretty much same as "Assigned to you" ### Screenshots _No response_
GiteaMirror added the issue/needs-feedback label 2025-11-02 08:01:53 -06:00
GiteaMirror commented 2025-11-02 08:01:54 -06:00
Author
Owner
Copy Link

@aceArt-GmbH commented on GitHub (Jun 20, 2023):

This would be a nice addition for project managers to see how much their colleagues have on their plate.
You can already see the tickets in a repository, but not across multiple/all repos

image

Either "Assigned to you" could have the "you" be a dropdown.
Or next to the team dropdown?

@aceArt-GmbH commented on GitHub (Jun 20, 2023): This would be a nice addition for project managers to see how much their colleagues have on their plate. You can already see the tickets in a repository, but not across multiple/all repos ![image](https://github.com/go-gitea/gitea/assets/33117017/667f1146-0f86-4282-9617-8bd0d0250aa7) Either "Assigned to you" could have the "you" be a dropdown. Or next to the team dropdown?
GiteaMirror commented 2025-11-02 08:01:54 -06:00
Author
Owner
Copy Link

@GiteaBot commented on GitHub (Sep 8, 2023):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Sep 8, 2023): We close issues that need feedback from the author if there were no new comments for a month. :tea:
GiteaMirror commented 2025-11-02 08:01:54 -06:00
Author
Owner
Copy Link

@aceArt-GmbH commented on GitHub (Sep 11, 2023):

This ticket does not need feedback from the author, but rather from the gitea team how it should be implemented

@aceArt-GmbH commented on GitHub (Sep 11, 2023): This ticket does not need feedback from the author, but rather from the gitea team how it should be implemented
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/needs-feedback
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#8309
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?