Issue "New Branch" shouldn't include full title of confidential issue
Right now the branch title will be possibly-sensitive-issue-title-123 where 123 is the issue ID.
For confidential issues, it should be a simple issue-123.
Of course the commits themselves could still give the vulnerability away, but chances are relatively small people will read every commit and branch, and commits can be carefully named to be technically accurate but not give away that it fixes a vulnerability
cc @zj
Activity
mentioned in issue #14567 (moved)
There should be some way to set the title instead of GitLab deciding it for you. The case also in #14590 (moved). If we know how to do this, we should set a milestone I guess? (Thats up to you of course
Milestone changed to 8.7
cc @dbalexandre
@zj That's a different issue :)
Reassigned to @timothyandrew
mentioned in merge request !3671 (merged)
mentioned in commit 5d88de09
mentioned in issue #3886 (closed)
Status changed to closed by commit 18a8844f
mentioned in commit 18a8844f
