Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Changing Default Sort for Gitlab Issues

Tags:

sorting

gitlab

Is there a way of changing the default sort in Gitlab issues tracker from "Newest" to "Recently Updated"?

I understand I can change it by just selecting the sort filter, however, doing this every time becomes annoying quickly.

like image 571
STOIE Avatar asked Jul 16 '14 05:07

STOIE


People also ask

What is sort default?

By default, the order by statement will sort in ascending order if no order (whether ascending or descending) is explicitly specified. This means that because the default sort order is ascending, the values will be sorted starting from the “smallest” value to the largest.

What is weight in GitLab issue?

With weighted issues, you can get a better idea of how much time, value, or complexity a given issue has or costs. You can set the weight of an issue during its creation, by changing the value in the dropdown menu. You can set it to a non-negative integer value from 0, 1, 2, and so on.

What are GitLab issues?

Issues are a core building block in GitLab that enable collaboration, discussions, planning and tracking of work. Planning an aspect of an event or a campaign.


1 Answers

does anyone know if there is a way of changing the default sort in Gitlab issues tracker from "Newest" to "Recently Updated"

Not that I know of (mid 2014):

  • there is no issue in the GitLab CE project
  • the one issue in GitHub GitLab project (April 2014) refers to the GitLab CE project
  • There are a few suggestions, but none regarding the default sorting order
  • there is nothing in the main config gitlab.yml file

That could be a good PR (Pull Request) to make, starting with:

  • app/helpers/issues_helper.rb, which sorts issues by name
  • app/models/project.rb, which also sorts issues by name
  • app/views/projects/issues/_issue.html.haml which lists issues by name

Update January 2016: as mentioned by stevenw00 in the comments, there is now issue 5546

As a user frequently viewing a list of issues (or merge requests), I want to be able to have the list sort I use remembered, so that I do not have to constantly set the sort when ever I view a list of issues (or merge requests).


Update Dec. 2018 with GitLab 11.6

Per-user saved sort order in issues, merge requests, and epics

There are now user-specified sort order selections in issues, merge requests, epics, and even roadmap views.
Which type of attribute you choose to sort by, and in which order you choose to sort (ascending or descending), is saved to the system, so that when you return to the same type of object list, it will remain what you have selected previously.

https://about.gitlab.com/images/11_6/sort-order.png


Update August 2019, GitLab 12.2

Manual Issue List Sorting

As of 12.2, you can now sort an Issue List in Manual mode, which allows you to drag and drop Issues within the list to assign them a relative order.

https://about.gitlab.com/images/12_2/manual-issue-sorting.gif

The order is persisted and maintained across the entire instance for all Project Issue Lists and Group Issue Lists that have Manual mode enabled

See documentation and issue.


With GitLab 13.7 (December 2020), you have a new (non-free) option:

Sort issues by the number of issues they are blocking

While prioritizing a list of issues in GitLab, it’s often important to determine the critical path and whether an issue is blocking other issues.

With the current issue list, it is impossible to see which issues are blocking other issues. The only way to do so is to open each one and see the list of blockers below the issue description, which is a very time-consuming task!

As of 13.7, you can now use the filter for “Blocking” on any issue list, and you will see a list sorted by the number of blockers.

https://about.gitlab.com/images/13_7/sort-issues-by-blockers.png -- Sort issues by the number of issues they are blocking

See Documentation and Issue.

like image 104
VonC Avatar answered Sep 30 '22 06:09

VonC