Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 44,093
    • Issues 44,093
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,359
    • Merge requests 1,359
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #262877
Closed
Open
Created Oct 06, 2020 by Amanda Rueda@amandarueda🎳Developer

BE: Seats Currently in Use Members List - export members list

Summary

This is a follow-up iteration to the work completed in #216899 (closed).

In this issue, we will provide users ability to export a list of billable users.

Success Criteria

  1. The export should be a filterable file format. (ex. csv - but open to other suggestions)
  2. The data presented in the UI, Seat Usage page, should be represented in the export file.
  3. If the file cannot be made available immediately, it can also be emailed to the user with a success message in-app at time of request. (Attn - during breakdown if this is needed, please let me know so I can get UX on the success message)

Designs

#282548 (closed)

Availability & Testing

A Controller spec should be added to account for the "export" view/action. The spec should validate that the MIME type is correct (e.g., if we send an CSV file, the MIME should be text/csv and the extension ends in .csv. No need to validate the file contents.

Edited Apr 26, 2021 by Amanda Rueda
Assignee
Assign to
Time tracking