Skip to content

GitLab Next

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

Closed
Open
Opened Apr 15, 2020 by Mark Wood@mjwood🌀Developer

Capture Interactions with Requirements

Problem

As Category:Requirements Management becomes more mature, we want to transition from measuring success based on number of requirements created to interactions with requirements.

A general workflow for teams utilizing requirements would be as follows:

  1. Create high level requirements (requirements at a group level) - not yet implemented in GitLab
  2. Create low level requirements (requirements at a project level) - Implemented in GitLab %12.10
  3. Develop design / code / testing by referencing requirements
  4. Link appropriate design / code / test to requirements - Test linking MVC in %13.1

In short, the actual creation of requirements is only a small piece of capturing the benefits of having a requirements based development approach - the far greater measure of success is to measure the interactions with requirements - specifically viewing and tracing to requirements.

Proposal

After we are able to achieve requirement creation metrics via Usage Ping, we would like to plan out and implement the next steps as follows:

  1. Track requirement navigation changes - are users paging through requirements?
  2. Track requirements filter events - are users searching for requirements to reference them?
  3. Track linking events - are users linking both code and tests to requirements?

Result

Next steps (if any)

Edited Jun 24, 2020 by Mark Wood
Assignee
Assign to
13.7
Milestone
13.7 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/product-intelligence#370