A user should be able to filter issues based on whether the issue is confidential or not.
Further details
Currently, issues can not be filtered by whether they are confidential or not.
Proposal
Implement a filter for confidential:true similar to the other issue filters. confidential:true and confidential:false should be available. present and yes should be accepted as synonyms for true
What does success look like, and how can we measure that?
Usage data and traffic will show use of the confidential filter.
Links / references
This is related to #17326 (closed), which focused on search visibility and #29784 (moved) which has a scope much larger then this MVC.
Reporting: A team is asked to report how many of their issues are confidential/not confidential and how that is changing over time. This is a current task I have that requires exporting issues into a tool like splunk or use the API to retrieve all issues for a project and perform the count.
Confidential issues tend to be higher priority regardless of user defined labels, so filtering on confidential provides a de facto way to list higher priority issues.
For admins, being able to view an issue list as it is shown to external users is helpful for auditing access.
LGTM! True and False could also work, but looks like we're going with Yes/No for WIP MRs, so let's keep it consistent. Will update the description shortly
Updated the description. @victorwu what do you think about confidential:yes/no as the filter option? Or maybe confidential:state or confidential:boolean
@annabeldunstone: I think confidential:Yes/No looks good, making it consistent with the dropdown values. (i.e. capitalized). But I also see it's different in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/18119. Why don't you make the final decision and then let's create a separate issue if necessary so that they are consistent in both places.
Also, you used the eye icon for the icon. Should it be the icon where there is a slash through it indicating that it is confidential?
And lastly, do you think it should be last item in the dropdown? Maybe at least about the emoji filter one? Or we can just stick it wherever and have a separate issue to discuss the order of the items.
@victorwu I think it looks best for the token dropdown to be all in lowercase (to match the rest of the options), like in the current mockup, and for the actual value dropdown to be capitalized Yes and No
Also, you used the eye icon for the icon. Should it be the icon where there is a slash through it indicating that it is confidential?
Yes it should
And lastly, do you think it should be last item in the dropdown?
Since this was the most recent requested filter option, I assumed it isn't used as often as the others, and should be last. However, the list is close to alphabetical order, so we could go in that direction too. I don't think it's super important at the moment as there aren't too many options, so I'm open to changing it.
#50747 (comment 97125566)
Recently I started to use 'Gitbook' + 'GitLab Pages' + 'GitLab Issues' to maintain the technical documents of my team in place of a knowledge-based system.
When I reorganized the documents, I found some of them are out of date. Although they shouldn't be shown to users, they should be kept as historical documents. Then I created a confidential issue for each historical document and created a non-confidential issue for each usefule one.
In order to quickly list all of non-confidential issues , I need the filter funciton.