forge/forge
9
7
Fork 5
Code Issues 87 Pull requests Projects 2 Wiki Activity Actions

Private Issues, Web UI: List the private issues in its separate section #495

New issue
Open
opened 2026-04-07 03:26:15 +00:00 by t0xic0der · 4 comments
t0xic0der commented 2026-04-07 03:26:15 +00:00
Member
Copy link

Summary

Private Issues, Web UI: List the private issues in its separate section

Details

Private Issues, Web UI: List the private issues in its separate section

Associated with issue forge/forge#442

### Summary Private Issues, Web UI: List the private issues in its separate section ### Details Private Issues, Web UI: List the private issues in its separate section Associated with issue forge/forge#442
t0xic0der added this to the Backlog project 2026-04-07 03:26:16 +00:00
t0xic0der modified the project from Backlog to Sprint 18 2026-04-07 10:15:53 +00:00
t0xic0der commented 2026-04-08 04:46:56 +00:00
Author
Member
Copy link

We need to complete forge/forge#464 before we start with this.

We need to complete forge/forge#464 before we start with this.
t0xic0der commented 2026-04-14 05:51:21 +00:00
Author
Member
Copy link

I made some headway with the frontend implementation 😭

image

I do not like it though. It is very experimental. We could prolly do it better.

The new issue button does not work for now. Or at least, how I want it.

The count bubble is visible only to those who have the necessary access.

Other authenticated user can view that panel but this would up empty.

image

For users opening a private issue there, only their count would be shown.

While the repo owner or those having the access, get to see everything.

The issue index is also shared with the normal publicly visible issues.

You wanna see the code changes? Nope, still some polishing needed.

I made some headway with the frontend implementation 😭 ![image](/attachments/4f00df06-20e6-4c2e-829d-ed0615b76797) I do not like it though. It is very experimental. We could prolly do it better. The new issue button does not work for now. Or at least, how I want it. The count bubble is visible only to those who have the necessary access. Other authenticated user can view that panel but this would up empty. ![image](/attachments/6b71e20a-12f9-487d-9f3a-0f6cfec7e1b3) For users opening a private issue there, only their count would be shown. While the repo owner or those having the access, get to see everything. The issue index is also shared with the normal publicly visible issues. You wanna see the code changes? Nope, still some polishing needed.
image.png
82 KiB
image.png
73 KiB
t0xic0der commented 2026-04-15 07:02:23 +00:00
Author
Member
Copy link

I am retaining the issue ticket assigned points for now on an evaluation.

For what its worth, this implementation has too many moving pieces to tackle before it becomes functional.

image

Following the conversation with @ryanlerch from this morning's meeting, we would want to have a common listing for both public issues and private issues. Depending on the access levels, all the issue tickets (including public and private) should be visible to the owners and maintainers, the private issue ticket reporters should see the public tickets and only the private tickets that they opened or are involved in, and the third person should see only the public tickets. The count shown on the tab headers inside the pill also needs to be modified to reflect the same and those within the open, closed and all sections need to be changed too.

Fingers crossed.

I am retaining the issue ticket assigned points for now on an evaluation. For what its worth, this implementation has too many moving pieces to tackle before it becomes functional. ![image](/attachments/ec51a1fc-126d-471c-9a03-8a84f9a4e4e1) Following the conversation with @ryanlerch from this morning's meeting, we would want to have a common listing for both public issues and private issues. Depending on the access levels, all the issue tickets (including public and private) should be visible to the owners and maintainers, the private issue ticket reporters should see the public tickets and only the private tickets that they opened or are involved in, and the third person should see only the public tickets. The count shown on the tab headers inside the pill also needs to be modified to reflect the same and those within the open, closed and all sections need to be changed too. Fingers crossed.
image.png
82 KiB
nphilipp commented 2026-04-15 09:36:42 +00:00
Member
Copy link

we would want to have a common listing for both public issues and private issues

Hmm, I would like this too, but: Because public and private issues are in separate tables, querying either are separate activities. I.e., right now there’s no way to say “give me public and private issues from the point of view of this user, paginated” in one go. I can think of several approaches to tackle this, all with their own downsides 😉:

  • Refactor pagination: instead of expressing “give me page number X of pages of size Y”, you would say “give me Y results with and index > Z”, where index is the user-visible number of an issue. The big downside is that we would lose the notion of “page” because indexes are shared between issues and pull requests, e.g. 20 consecutive issues would usually take up more indexes than 20. I don’t think that upstream would accept this.
  • Make a join over the results of queries to both tables in one query. This could work because both tables have the same structure if you ignore the order of columns, but we would essentially have to bypass the ORM and hand-craft the query, which makes it much harder to maintain. Also, I think it’s likely to have a negative impact on query performance.
> we would want to have a common listing for both public issues and private issues Hmm, I would like this too, but: Because public and private issues are in separate tables, querying either are separate activities. I.e., right now there’s no way to say “give me public and private issues from the point of view of this user, paginated” in one go. I can think of several approaches to tackle this, all with their own downsides 😉: - Refactor pagination: instead of expressing “give me page number X of pages of size Y”, you would say “give me Y results with and index > Z”, where index is the user-visible number of an issue. The big downside is that we would lose the notion of “page” because indexes are shared between issues and pull requests, e.g. 20 consecutive issues would usually take up more indexes than 20. I don’t think that upstream would accept this. - Make a join over the results of queries to both tables in one query. This could work because both tables have the same structure if you ignore the order of columns, but we would essentially have to bypass the ORM and hand-craft the query, which makes it much harder to maintain. Also, I think it’s likely to have a negative impact on query performance.
humaton modified the project from Sprint 19 to Sprint 20 2026-05-05 10:19:29 +00:00
humaton modified the project from Sprint 20 to Sprint 21 2026-05-18 10:16:07 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
test
docs
No results found.
Labels
Clear labels   
Backlog Status
Needs Review
 Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  
Backlog Status
Ready
 Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and could be worked on immediately when capacity is available.

  
Chore
Tasks that are necessary but don't directly deliver new value to the end-user. These are internal tasks like updating a library, managing user accounts, or setting up a new service.

  
points
01
 A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  
points
02
 This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  
points
03
 medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  
points
05
 a significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  
points
08
 complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  
points
13
 Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint.

  
Priority
High
 This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  
Priority
Low
 This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  
Priority
Medium
 This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  
Sprint Status
Blocked
 Indicates the work cannot proceed. There is a dependency or an issue that is preventing the team from completing the task. This is a flag for the Scrum Master to help unblock the team.

  
Sprint Status
Done
 Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  
Sprint Status
In Progress
 This label is for work that a developer is actively working on. This is usually what you'll see on the "In Progress" column of your project board.

  
Sprint Status
Review
 This indicates that the work is complete, but it is now in a review state. This could mean a peer code review, a QA check, or a review by the Product Owner.

  
Sprint Status
To Do
 Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  
Technical Debt
work that improves the codebase without adding new features. It's work that pays down the "debt" you've accumulated, such as refactoring a messy piece of code, improving test coverage.

  
Work Item
Bug
 Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  
Work Item
Epic

  
Work Item
Spike

  
Work Item
Task

  
Work Item
User Story

No labels
Backlog Status
Needs Review
Backlog Status
Ready
Chore
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Sprint 21
Assignees
Clear assignees
No assignees
t0xic0der
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#442 Private Issues, Web UI: List and read private issues
forge/forge
Depends on
#464 Create shared branch in Fedora forgejo fork
forge/forge
Reference
forge/forge#495
No description provided.