Skip to content

GitLab Next

    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Menu
    Projects Groups Snippets
  • Get a free trial
  • Sign up
  • Login
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 43,068
    • Issues 43,068
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,360
    • Merge requests 1,360
  • 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.org
  • GitLabGitLab
  • Issues
  • #16565
Closed
Open
Created Nov 25, 2016 by Sean McGivern@smcgivernMaintainer

Create sub-todos / todo events

When you have an active todo for a target (typically an issue or an MR), you won't get a new todo for that same event.

However, it would be very handy to know:

  1. How many times todo-creating events have been issued on that target. (In general, the higher, the more important.)
  2. Which todo was most recently bumped.
  3. If a todo of a 'regular' type (mention) was later superseded by an 'important' type (build failed, assigned, etc.).

This means that we could allow sorting todos on updated_at, but we'd also show the todo if a filter on type matched any of the types in the sub-todo / todo events table. I think we could use some gitlab-ce~2024184 here, but I understand how the backend would work, at least 🙂 @pedroms and @dbalexandre, what do you think?

This replaces https://gitlab.com/gitlab-org/gitlab-ce/issues/23293.

Edited Sep 02, 2020 by 🤖 GitLab Bot 🤖
Assignee
Assign to
Time tracking