#### Problem Understanding how source code changes over time is one of the key problems the source code UI attempts to solve. There are a number of different features and navigational paths for accessing history. We should evaluate if this current organization and navigation between them is the optimal experience to solve the JTBD. **JTBD statement**: When changes are introduced into my project, I want to track those changes over time, so I can understand the impact they are having. Current options for seeing "history" - Commits - Blame - Graph - Tags (subset of history) - Merge request (subset of history) #### Proposal Design an experience for history based on the users JTBD