Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Merge requests
  • !9938

Better priority sorting

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Sean McGivern requested to merge better-priority-sorting into master Mar 14, 2017
  • Overview 29
  • Commits 2
  • Pipelines 4
  • Changes 25

What does this MR do?

  1. Change the priority sort to be milestone due date soonest + label priority.
  2. Add a 'started' filter for milestones, which returns results from all milestones with a start date less than or equal today.

Are there points in the code the reviewer needs to double check?

All of it?

Why was this MR needed?

We had to create Next Patch Release to work around this limitation.

Screenshots (if relevant)

image

Does this MR meet the acceptance criteria?

  • Changelog entry added
  • Documentation created/updated
  • Tests
    • Added for this feature/bug
    • All builds are passing
  • Conform by the merge request performance guides
  • Conform by the style guides
  • Branch has no merge conflicts with master (if it does - rebase it please)
  • Squashed related commits together

What are the relevant issue numbers?

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/28754.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: better-priority-sorting