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:

Want to help? Learn how to contribute to Fedora Docs ›