6

I can't find a 'create branch' button in the page; guessing I am missing something obvious?

enter image description here

from gitlab members section, I myself is displayed as 'maintainer' of the project; I initially imported this project from a github repo using github url. Is this expected?

==== 2020.07.05 ======

answering myself: in my case, the issues was created from a defect reported by github application security analysis CI run, and it is automatically marked as 'confidential', and for confidential issue, by default, there is no action available to create merge request and feature request.

in order to enable MR, I had to edit the 'confidentiality' label to toggle it off.

enter image description here

I am using gitlab.com and version below:

enter image description here

sqr
  • 365
  • 2
  • 12
  • 29
  • Good catch. You actually can add an answer, and select your self-answer as accepted. – VonC Jul 05 '20 at 14:32

2 Answers2

4

Make sure you are logged in to GitLab, as a owner/collaborator of the repository.
And of course, I assume you are using GitLab 8.6+, since that button was introduced in 8.6 (issue 3886).

Check if you see (on the Issue screen), a green button labeled "Create a merge request", with a down-arrow to its right.
That would be dropbox which includes the "Create Branch" option.

Create MR

An alternative would be locally (in your local clone) to create a branch named "<issue-number>-issue-description" and push it to GitLab: that would create and associate that branch to the issue.

Plus, with GitLab 15.0 (May 2022)

Internal notes

In many cases, organizations want to keep issues and epics public, but apply stricter governance to conversations within them. For example, when using GitLab issues as part of Service Desk workflows, organizations may want to make core details about an issue public, but not to expose customer-specific confidential data broadly.

With internal notes, you can redact discussions with internal or customer data that should only be visible to certain users, while keeping the core details about an issue public. Internal notes in issues or epics can only be seen by the issue author, assignee, and group or project members with at least the Reporter role.

Thanks @leetickett for collaborating with our team on this feature!

https://about.gitlab.com/images/15_0/add_internal_note_v15_0.png -- Internal notes

See Documentation and Epic.

See also GitLab 15.6 (November 2022)

Prevent Guests from viewing internal notes

Internal notes provide organizations with a way to manage internal communication in an issue or epic.

We have improved support for this use case by ensuring users with the Guest role cannot create or view internal notes on GitLab issues and epics, even if they are the assignee or the author for that issue or epic.

This provides organizations assurance that information in their internal notes will only be visible to members of their organization.

See Documentation and Issue.

VonC
  • 1,262,500
  • 529
  • 4,410
  • 5,250
  • thanks. I myself is displayed a 'maintainer' to my project. is there something wrong with my settings somewhere? – sqr Jul 05 '20 at 02:23
2

answering myself: in my case, the issues was created from a defect reported by github application security analysis CI run, and it is automatically marked as 'confidential', and for confidential issue, by default, there is no action available to create merge request and feature request.

in order to enable MR, I had to edit the 'confidentiality' label to toggle it off.

sqr
  • 365
  • 2
  • 12
  • 29