Proposal: Weighted Issues #13504

New Issue

GiteaMirror · 2025-11-02T10:44:38-06:00

GiteaMirror commented

2025-11-02 10:44:38 -06:00

Originally created by @maantje on GitHub (Sep 18, 2024).

Introduce the ability to assign weights to issues, allowing teams to prioritize and allocate work based on effort. This feature would enhance project management capabilities by enabling better planning and tracking within projects.

Currently, Gitea issues lack the ability to assign weight or effort to an issue. This limitation makes it difficult for teams to:

Estimate the time and effort needed to complete different tasks.
Balance workload distribution across team members and milestones.

Mentions:

Proposed Solution:

Add an opt-in feature to Gitea Issues allowing users to assign a weight to each issue. This weight would represent the effort of the issue. Key features of this proposal include:

Adding Opt-in Configuration Option
The following configuration options will control the weight feature, allowing users to opt into using weighted issues.

ENABLE_ISSUE_WEIGHT: false       # Enable/Disable weight feature
DEFAULT_ENABLE_ISSUE_WEIGHT: true # Default enable/disable weight feature during repository creation

Adding Weight to Issues:
Users can assign weights to issues directly upon creation from the issue sidebar. This allows quick assignment of effort to tasks without navigating away from the issue creation page.
Editing Weights:
Weights can be updated at any point during issue edits, with the weight field being easily accessible from the sidebar in the issue details view.
Weight Change Tracking:
Automatic comments are generated for weight-related changes, documenting the addition, modification, or removal of weights.
Milestone Weight Progress:
Milestones display total weight for all associated issues. Progress bars are based on the sum of weights rather than just issue counts, providing a clearer view of the actual effort remaining.
Project Board Integration:
On project boards, issues display their weight, and columns show the total weight of issues within them, allowing teams to balance workloads effectively. Filters help further refine issue distribution across the board.

I made a basic proof of concept, visible here, to get familiar with the codebase and assess the complexity of implementing the necessary changes.

Screenshots

Issue

Milestone

Project

Originally created by @maantje on GitHub (Sep 18, 2024). Introduce the ability to assign weights to issues, allowing teams to prioritize and allocate work based on effort. This feature would enhance project management capabilities by enabling better planning and tracking within projects. Currently, Gitea issues lack the ability to assign weight or effort to an issue. This limitation makes it difficult for teams to: - Estimate the time and effort needed to complete different tasks. - Balance workload distribution across team members and milestones. ### Mentions: - https://github.com/go-gitea/gitea/issues/10440 - https://github.com/go-gitea/gitea/issues/19001 - https://github.com/go-gitea/gitea/issues/16572 ### Proposed Solution: Add an opt-in feature to Gitea Issues allowing users to assign a weight to each issue. This weight would represent the effort of the issue. Key features of this proposal include: - **Adding Opt-in Configuration Option** The following configuration options will control the weight feature, allowing users to opt into using weighted issues. ```bash ENABLE_ISSUE_WEIGHT: false # Enable/Disable weight feature DEFAULT_ENABLE_ISSUE_WEIGHT: true # Default enable/disable weight feature during repository creation ``` - **Adding Weight to Issues**: Users can assign weights to issues directly upon creation from the issue sidebar. This allows quick assignment of effort to tasks without navigating away from the issue creation page. - **Editing Weights**: Weights can be updated at any point during issue edits, with the weight field being easily accessible from the sidebar in the issue details view. - **Weight Change Tracking**: Automatic comments are generated for weight-related changes, documenting the addition, modification, or removal of weights. - **Milestone Weight Progress**: Milestones display total weight for all associated issues. Progress bars are based on the sum of weights rather than just issue counts, providing a clearer view of the actual effort remaining. - **Project Board Integration**: On project boards, issues display their weight, and columns show the total weight of issues within them, allowing teams to balance workloads effectively. Filters help further refine issue distribution across the board. I made a basic proof of concept, visible [here](https://github.com/maantje/gitea/pull/1/files), to get familiar with the codebase and assess the complexity of implementing the necessary changes. ### Screenshots #### Issue ![Screenshot 2024-09-18 at 18 36 52](https://github.com/user-attachments/assets/016b43d6-745d-46c7-901a-75ee3f69b83b) ![Screenshot 2024-09-18 at 18 37 24](https://github.com/user-attachments/assets/8508b480-e0c4-4bb1-a705-5e41d677926d) ![Screenshot 2024-09-18 at 18 38 57](https://github.com/user-attachments/assets/72bdf56c-3b40-4fad-9b34-b9bf2930f65d) ![Screenshot 2024-09-18 at 18 39 07](https://github.com/user-attachments/assets/a926f806-c0b5-4918-858b-b49b9fee038e) ![Screenshot 2024-09-18 at 18 39 43](https://github.com/user-attachments/assets/a2b9965e-2b13-42ed-a7c3-5ae2a53a91f2) #### Milestone ![Screenshot 2024-09-18 at 18 49 33](https://github.com/user-attachments/assets/fe717286-82cb-4bda-8588-edbb0c140b3b) ![Screenshot 2024-09-18 at 18 50 52](https://github.com/user-attachments/assets/5869d455-b61d-45b9-a324-bd8784aacf42) #### Project ![Screenshot 2024-09-18 at 18 53 28](https://github.com/user-attachments/assets/1ce56ba2-d909-4830-9566-44b63732a252) ![Screenshot 2024-09-18 at 18 55 11](https://github.com/user-attachments/assets/281d44e6-6f50-4c93-abb4-7aa3a60fc98b)

GiteaMirror added the type/proposal label 2025-11-02 10:44:38 -06:00

GiteaMirror commented

2025-11-02 10:44:38 -06:00

@yp05327 commented on GitHub (Sep 18, 2024):

It seems that you have already implemented it. Can you send a PR? Thanks!

@yp05327 commented on GitHub (Sep 18, 2024): It seems that you have already implemented it. Can you send a PR? Thanks!

GiteaMirror commented

2025-11-02 10:44:39 -06:00

@lunny commented on GitHub (Apr 10, 2025):

Is this resolved by #33206?

@lunny commented on GitHub (Apr 10, 2025): Is this resolved by #33206?

GiteaMirror commented

2025-11-02 10:44:39 -06:00

@wxiaoguang commented on GitHub (Apr 10, 2025):

Is this resolved by #33206?

NO

@wxiaoguang commented on GitHub (Apr 10, 2025): > Is this resolved by [#33206](https://github.com/go-gitea/gitea/pull/33206)? NO

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#13504