Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • XSweet XSweet
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 53
    • Issues 53
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • XSweetXSweet
  • XSweetXSweet
  • Issues
  • #166
Closed
Open
Issue created May 03, 2020 by Alex Theg@athegOwner

Track changes for tables?

Tracking changes to tables came up in this week's discussion with @bharathydasan and @wendell. There may not ultimately be a need for this, but if there is, it can come after the initial TC implementation.

This could also be potentially very complex. @wendell suggested that as a way to limit the scope/complexity of a solution, a simple whole-table before/after comparison could be surfaced, rather than a granular representation of the specific changes.

Assignee
Assign to
Time tracking