t0xic0der/forge-documentation
1
0
Fork 0
forked from forge/documentation
Code Pull requests Activity

Add known issue documentation for organization projects

Browse source 
Documents issue #139 where adding repository issues to organization-level projects fails silently when the Projects unit is disabled at the repository level. Includes problem description, symptoms, root cause, workaround steps, and upstream status with links to bug report and fix PR.
This commit is contained in:
Ryan Lerch 2025-10-02 19:19:18 +10:00
commit 5a5d256af6
2 changed files with 35 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

1
modules/ROOT/nav.adoc
View file

@ -14,3 +14,4 @@
** xref:creating_a_new_team.adoc[Creating a new Team]
* Known Issues
** xref:known_issue_cannot_create_user.adoc[Unable to Log in - "Cannot Create Account"]
** xref:known_issue_organization_projects.adoc[Adding Issues to Organization Projects Doesn't "Stick"]

34
modules/ROOT/pages/known_issue_organization_projects.adoc Normal file
View file

@ -0,0 +1,34 @@
= Known Issue: Adding Issues to Organization Projects Doesn't "Stick"
== Problem Description
There is a known issue in Forgejo that affects the ability to add repository-level issues to organization-level projects. If the Projects unit is disabled at the repository level, any attempt to add an issue from that repository to an organization-level project will fail silently. The change will appear to not "stick" after you save it.
== Symptoms
* You try to add an issue from a repository to an organization-level project
* The assignment appears to work initially
* After saving or refreshing, the issue is no longer assigned to the project
* No error message is displayed
== Root Cause
This occurs when the Projects unit is disabled in the repository settings where the issue is located. Even though you're trying to add the issue to an organization-level project (not a repository-level project), Forgejo still requires the Projects unit to be enabled at the repository level.
== Workaround
To successfully add issues to an organization-level project:
1. Navigate to the repository settings where the issue is located
2. Go to the "Features" or "Units" section
3. Enable the "Projects" unit for that repository
4. Once enabled, you can then add issues from that repository to any organization-level project
The Projects unit only needs to be enabled - you don't need to actually create any repository-level projects.
== Upstream Status
This is a recognized upstream issue:
* **Bug report**: https://codeberg.org/forgejo/forgejo/issues/5666[forgejo/forgejo#5666]
* **Fix in progress**: https://codeberg.org/forgejo/forgejo/pulls/7999[forgejo/forgejo#7999]