github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-07-10 16:44:50 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Allow multiple projects per issue #6068

New Issue
Open
opened 2025-11-02 06:44:11 -06:00 by GiteaMirror · 8 comments
GiteaMirror commented 2025-11-02 06:44:11 -06:00
Owner
Copy Link

Originally created by @MGChecker on GitHub (Sep 29, 2020).

It would be really nice to be able to link an issue to multiple kanban boards.

Originally created by @MGChecker on GitHub (Sep 29, 2020). It would be really nice to be able to link an issue to multiple kanban boards.
GiteaMirror added the topic/projectstype/proposal labels 2025-11-02 06:44:11 -06:00
GiteaMirror commented 2025-11-02 06:44:12 -06:00
Author
Owner
Copy Link

@6543 commented on GitHub (Sep 29, 2020):

Backend (DB shema) support it. It would only require work in the frontend and a modify some go files :)

@6543 commented on GitHub (Sep 29, 2020): Backend (DB shema) support it. It would only require work in the frontend and a modify some go files :)
GiteaMirror commented 2025-11-02 06:44:12 -06:00
Author
Owner
Copy Link

@tyroneyeh commented on GitHub (Jun 10, 2022):

Hello,

You can try this modification, but you can only select multiple projects after creating an issue. I don't know why it doesn't work for multiple choice in the new issue.

Patch diff:

  • 716fde369cd5a000580fc0e0f8a9a8337becb94f
  • cc11e8ff83e7a4fdbbc8efeb777117563de3b99a
  • 72c3764ab6d2e30954e37f6084d257edff33a786
  • ec4546a7845a2f68ca03f183f71f44b1b37e2769

image

image

@tyroneyeh commented on GitHub (Jun 10, 2022): Hello, You can try this modification, but you can only select multiple projects after creating an issue. I don't know why it doesn't work for multiple choice in the new issue. Patch diff: - 716fde369cd5a000580fc0e0f8a9a8337becb94f - cc11e8ff83e7a4fdbbc8efeb777117563de3b99a - 72c3764ab6d2e30954e37f6084d257edff33a786 - ec4546a7845a2f68ca03f183f71f44b1b37e2769 ![image](https://user-images.githubusercontent.com/1255041/173081128-d5135bdb-0ca8-4f38-8791-4071195df17a.png) ![image](https://user-images.githubusercontent.com/1255041/173081072-dfed8fa3-8214-4f2c-8805-af74f6b9ac64.png)
GiteaMirror commented 2025-11-02 06:44:13 -06:00
Author
Owner
Copy Link

@univai commented on GitHub (Oct 13, 2022):

Is this the recommended way to go? Or are their other issues one ought to be tracking?

@univai commented on GitHub (Oct 13, 2022): Is this the recommended way to go? Or are their other issues one ought to be tracking?
GiteaMirror commented 2025-11-02 06:44:13 -06:00
Author
Owner
Copy Link

@PMX-Alexis commented on GitHub (Jun 8, 2023):

Any update coming regarding this issue?

@PMX-Alexis commented on GitHub (Jun 8, 2023): Any update coming regarding this issue?
GiteaMirror commented 2025-11-02 06:44:13 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jun 8, 2023):

Nobody are working on this.

@lunny commented on GitHub (Jun 8, 2023): Nobody are working on this.
GiteaMirror commented 2025-11-02 06:44:13 -06:00
Author
Owner
Copy Link

@tyroneyeh commented on GitHub (Jun 9, 2023):

I created a PR #25164

@tyroneyeh commented on GitHub (Jun 9, 2023): I created a PR #25164
GiteaMirror commented 2025-11-02 06:44:14 -06:00
Author
Owner
Copy Link

@tyroneyeh commented on GitHub (Jun 13, 2023):

Hi @lunny ,

Could you review it for me? I have attached a test screen recording

Thanks

@tyroneyeh commented on GitHub (Jun 13, 2023): Hi @lunny , Could you review it for me? I have attached a test screen recording Thanks
GiteaMirror commented 2025-11-02 06:44:14 -06:00
Author
Owner
Copy Link

@KlavsKlavsen commented on GitHub (Jul 19, 2023):

that PR was closed - "conflict has arisen".. no further info ? :(

@KlavsKlavsen commented on GitHub (Jul 19, 2023): that PR was closed - "conflict has arisen".. no further info ? :(
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 topic/projects type/proposal
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#6068
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?