-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Restricted Comments on Gitea #17822
Comments
Kinda related: #3217 |
|
Thank you for the reply! This comment would only show up for members of a team under a public issue with other public comments. Jira is great for those kind of service desk type issues and Gitea is more focused to be for complete Development which is why I am unsure if this feature fits this Project. Let me know what you think! |
This is also used on various bugzillas. For example, this is used at $DAYJOB when we have a public bug report, but with customer (or company) information that should not be public. |
We're using Gitea for several things now, it's great. Would be even cooler if this feature lands some day. FWIW in our case we just need a simple "private" flag we can set on a given comment. Which users can't see unless they have e.g. "can see private comments" permission on their team/role. Basically the same thing Redmine implemented here. Although if visibility is tied directly to certain team(s) when adding the comment, instead of simple flag, that would be fine too. Not sure if this is helpful info but wanted to add a +1 to the idea anyway. |
Feature Description
I think it would be great if Gitea had Restricted Comments similar to Jira.
https://confluence.atlassian.com/jirakb/add-restricted-comments-on-jira-962353957.html
Maybe Gitea could implement this on a Team basis.
If so I'd consider adding the ability to restrict a comment to multiple teams.
Let me know what you think of this or if you think this might be out of scope for this project (I don't even know if GitHub has this functionality).
Screenshots
The text was updated successfully, but these errors were encountered: