forge/forge
9
7
Fork 5
Code Issues 99 Pull requests Projects 3 Wiki Activity Actions

Private Issues, Web UI: Show the private issue ticket contents #496

New issue
Open
opened 2026-04-07 03:30:13 +00:00 by t0xic0der · 3 comments
t0xic0der commented 2026-04-07 03:30:13 +00:00
Member
Copy link

Summary

Private Issues, Web UI: Show the private issue ticket contents

Details

Private Issues, Web UI: Show the private issue ticket contents

Associated with issue forge/forge#442

### Summary Private Issues, Web UI: Show the private issue ticket contents ### Details Private Issues, Web UI: Show the private issue ticket contents Associated with issue forge/forge#442
t0xic0der added this to the Backlog project 2026-04-07 03:30:14 +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:58 +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:57:03 +00:00
Author
Member
Copy link

Here's some progress from the frontend implementation 🖌️

image

The repo owner and those having the access can see the contents of the ticket.

It has features of the a normal ticket because that is exactly where I derived this from.

I am yet to test things out like attachments, labels, milestones, projects, participants etc.

I want to see if changing anything from the above leads to the ticket to be exposed.

This would need some more time in the oven. I am not showing changes just yet.

Regarding the conversion of public tickets to privates ones (and vice versa), nope!

Here's some progress from the frontend implementation 🖌️ ![image](/attachments/1891861a-5870-4e92-95b8-459d4be8fd42) The repo owner and those having the access can see the contents of the ticket. It has features of the a normal ticket because that is exactly where I derived this from. I am yet to test things out like attachments, labels, milestones, projects, participants etc. I want to see if changing anything from the above leads to the ticket to be exposed. This would need some more time in the oven. I am not showing changes just yet. Regarding the conversion of public tickets to privates ones (and vice versa), nope!
image.png
113 KiB
t0xic0der commented 2026-04-15 06:54:24 +00:00
Author
Member
Copy link

I hereby increase the points assigned to this issue ticket from 5 to 8.

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

image

What if the creator assigns the private issue ticket a label and a person looks issue tickets up having that label? What if a milestone gets added to the issue ticket and it inadvertently ends up being visible to folks from the milestone listing? What happens to the ticket's visibility when it gets added to the project board? Do we make this ticket visible to folks that get referenced in the issue comments? Does a notification consisting of the private issue ticket contents get shared to them when someone gets referenced in either the issue body or issue comments? How would we treat the visibility to those whom we assign this issue ticket? What if someone references this private ticket (noticing the gap in the counting indices) under their public ticket as either a dependency or a dependent?

We need to ensure that the issue ticket remains accessible to only those to whom this should be accessible to, and hence, that would require for us to go through all these cases one by one to see if we are not leaving a hole to be exploited. Once we are able to achieve this, creating predictable test cases for these conditions could probably end up being a separate issue ticket altogether. All-in-all, this implementation is definitely not as easy as I thought it would be and we need to spend more efforts into getting it right.

I hereby increase the points assigned to this issue ticket from 5 to 8. For what its worth, this implementation has too many moving pieces to tackle before it becomes functional. ![image](/attachments/41b9bb79-461a-41b2-986a-251d5b6e0808) What if the creator assigns the private issue ticket a label and a person looks issue tickets up having that label? What if a milestone gets added to the issue ticket and it inadvertently ends up being visible to folks from the milestone listing? What happens to the ticket's visibility when it gets added to the project board? Do we make this ticket visible to folks that get referenced in the issue comments? Does a notification consisting of the private issue ticket contents get shared to them when someone gets referenced in either the issue body or issue comments? How would we treat the visibility to those whom we assign this issue ticket? What if someone references this private ticket (noticing the gap in the counting indices) under their public ticket as either a dependency or a dependent? We need to ensure that the issue ticket remains accessible to only those to whom this should be accessible to, and hence, that would require for us to go through all these cases one by one to see if we are not leaving a hole to be exploited. Once we are able to achieve this, creating predictable test cases for these conditions could probably end up being a separate issue ticket altogether. All-in-all, this implementation is definitely not as easy as I thought it would be and we need to spend more efforts into getting it right.
image.png
110 KiB
humaton modified the project from Sprint 19 to Sprint 20 2026-05-05 10:19:29 +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

  
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 can be worked on immediately when capacity is available.

  
chore

Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  
documentation

Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  
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 and should be broken down.

  
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
Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  
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
Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  
Sprint Status
Review
Work items that are complete but need review, testing, or approval before being marked as done.

  
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 addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

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

  
Work Item
Epic
Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  
Work Item
Spike
Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  
Work Item
Task
Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  
Work Item
User Story
User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

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
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
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 20
Assignees
Clear assignees
No assignees
t0xic0der
1 participant
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
#518 Private Issues, Web UI: Investigate and implement the milestone changes on a private issue
forge/forge
#519 Private Issues, Web UI: Investigate and implement the project changes on a private issue
forge/forge
#520 Private Issues, Web UI: Investigate and implement the assignee changes on a private issue
forge/forge
#521 Private Issues, Web UI: Investigate and implement the dependency changes on a private issue
forge/forge
#522 Private Issues, Web UI: Push the foundational private issues frontend codebase implementation
forge/forge
#523 Private Issues, Web UI: Investigate and implement the content changes on a private issue
forge/forge
Reference
forge/forge#496
No description provided.