GitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Enterprise Small Business Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream Management GitOpsGitLab Professional Services
Accelerate your software lifecycle with help from GitLab experts
Popular GitLab use cases
Enterprise Small Business Continuous Integration (CI/CD) Source Code Management (SCM) Out-of-the-box Pipelines (Auto DevOps) Security (DevSecOps) Agile Development Value Stream Management GitOpsThe project is accessible to all Support team members at https://uploader.gitlab.support (NOTE: currently, this requires both GitLab Pages and Okta authentication, both should happen automatically if you are signed in).
NOTE: Support Uploader exists as a Zendesk App for use while working tickets. For details, check the zendesk-app folder in the support-uploader
project.
These are the current defaults but may change in the future.
Input the ticket ID at https://uploader.gitlab.support and click "Generate files"
This will download an archive with the format "gs_uploader_
You can attach the archive generated to the ticket in a public reply, and use the General::Support uploader
macro, which will include instructions for the customer on how to use the bundled files.
There will be an automated private note by the "Support Uploader Bot" in the ticket for every file that the customer uploads with a link to the file in the AWS Support Uploader account.
The files are currently stores in an S3 bucket which all Support team members should have access to, you can use the link generated above to access it, which will be listed in the internal comment on the ticket.
Team members view:
AWS admin view:
A: This is expected behaviour. The normal way to access customer uploads will be via Zendesk ticket internal comments which will list the file upload link. (The IAM group for Support Engineers does not include the list buckets IAM permission which means you won't see the bucket from the root level of the S3 console).