Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 35,915
    • Issues 35,915
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,281
    • Merge Requests 1,281
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #31362

Closed
Open
Opened Aug 29, 2019 by Saswata Chakravarty@saswatac

Filter CI environment variables by their environment scope

Problem to solve

The UI for CI/CD settings displays a flat list for the environment variables. It is a common use case to have different values for the same variable in different environment scopes.

It will be a better user experience to view the environment variables filtered by their environment scopes.

Intended users

  • DevOps Engineer
  • Systems Administrator

Further details

Proposal

Either have a filter button that can be used to filter the list.

Alternatively have tabs for each environment, and clicking on the environment tab lists the available variables in that environment.

Permissions and Security

n/a

Documentation

Testing

What does success look like, and how can we measure that?

Links / references

Assignee
Assign to
Backlog
Milestone
Backlog
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#31362