2019-06-06 Newly created unlabelled issues requiring initial triage

Hi Triage Team,

Here is a list of the latest issues without labels in the project.

In accordance with the Level 1 triage guidelines, we would like to ask you to:

1. Check for duplicates in this project and others (it is common for issues reported in EE to already exist in CE).
2. Add a type label.

• If identified as a bug, add a severity label.
• If the severity is ~S1 or ~S2, mention relevant PM/EMs from the relevant stage group from product devstages categories.

1. Add a team label.
2. Add a stage label.
3. If possible, add relevant subject labels.
4. If needed, mention relevant domain experts if the issue requires further attention.

For the issues triaged please check off the box in front of the given issue.

Once you've triaged all the issues assigned to you, you can unassign yourself with the /unassign me quick action.

When all the checkboxes are done, close the issue, and celebrate! 🎉

@rymai

• #11983 (closed) Line-by-Line code coverage results displayed in a Merge Request's changes tab.

@tpazitny

• #11979 (closed) Move Dependency scanning reports logic for Pipelines to the backend

@sliaquat

• #11978 (closed) Move Container scanning reports logic for Pipelines to the backend

@godfat

• #11976 (closed) Move DAST reports logic for Pipelines to the backend

@tnikic

• #11970 (moved) Url for the next request with pagination is missing port

@mlapierre

• #11966 (moved) Job status is overwritable with the commit statuses API

@wlsf82

• #11947 (closed) Add Trivy as an option for Container Scanning

@zeffmorgan

• #11906 (closed) Running integration tests requiring credentials with auto devops