Sort issues by last comment

I'm not seeing any options for this: Sort issues list by date of last comment.

We have a few pages worth of issues open and unless everyone is subscribed to each issue, we'll have no idea if someone on the team is commenting on an issue until we stumble back on it.

Thanks!

Solution:

Comments should update the issue.

Good idea. Not sure if updated_at should do this, guess we don't touch the issue model (cc @dzaporozhets). Thanks @AksumkA

Milestone changed to 8.6

See also #3749 (closed).

mentioned in issue #3749 (closed)

@JobV Does Recently Updated sorting cover this case somehow already?

@creamzy Sorting by "Recently Updated" sorts by the updated date of the issue itself, and not by any comment. For example, https://gitlab.com/gitlab-com/operations/issues?assignee_id=&author_id=&label_name=&milestone_id=&scope=all&sort=updated_desc&state=opened currently sorts https://gitlab.com/gitlab-com/operations/issues/9 according to "updated about a month ago", while the latest comment is 8 days old.

Sorting by "Recently commented" (or something similar) would sort that issue much higher, according to the 8 days old comment.

@elygre true, thanks! I checked but obviously on a wrong issue

@creamzy BTW, when it comes to sorting issues, what I think is useful is sorting by newest of (issue updated) and (latest issue comment). Finding only the issues (as today) is obviously not enough. However, sorting only on latest issue comment would also miss updates to the issue itself.

IMHO, the natural thing is to consider a comment to be an issue update, so that the issue "timestamp" is the latest of (issue itself updated) and (issue comment created). I believe most other issue tracking systems use this definition.

@elygre

IMHO, the natural thing is to consider a comment to be an issue update, so that the issue "timestamp" is the latest of (issue itself updated) and (issue comment created). I believe most other issue tracking systems use this definition.

My first idea was it had been like that.Thank it why I made a mistake in previous comment. So I do agree with you, it will keep us from adding too many specific cases in the sorting.

@JobV what do you say about it?

@creamzy I'm with you. Comments should update the issue.

Added frontend label

mentioned in issue #826 (closed)

IMHO, the natural thing is to consider a comment to be an issue update, so that the issue "timestamp" is the latest of (issue itself updated) and (issue comment created). I believe most other issue tracking systems use this definition.

I agree. We should update issue when comment added. In this cause we can use existing sorting instead of adding new one

mentioned in issue #5601 (closed)

mentioned in issue #5588 (closed)

I agree with @dzaporozhets' comment and am closing #5588 (closed) as a duplicate of this ticket. I'm adding my votes here instead.

From #5588 (closed):

User Story

As a user viewing a list of issues (or merge requests), I want the "Updated N UNITS ago" info to take into account the comments, so that I can notice (from the list itself) what is getting attention.

IMO a merge request should also be considered updated if a new commit is pushed to the branch.

Just want to say that from my point of view @dzaporozhets proposed solution (https://gitlab.com/gitlab-org/gitlab-ce/issues/4113#note_3053648) would fit our needs perfectly. We are using gitlab extensively with non-tech persons as our main projectmanagement tool. We are trying to stress that our clients and partners try to keep the whole project-related communication in issues. As you can see in the attached screenshot, it is really difficult to find the currently changed issue, which in our case often is the exact same situation as "our client made a new comment"... We would have to track how many comments have been made. In the attached Screenshot, it is not visible, that the first 5 Issues have been commented in the last half hour, not to speak of the order in which the comments have been made! (The Issue that got "update 4 days ago" even became 2 new comments in the last hour)

@Leibniz137 I agree with your comment, though I think it probably warrants its own issue.

Some status update on votes feature https://gitlab.com/gitlab-org/gitlab-ce/issues/3763#note_3294222

@chRi____ I'm using Gitlab in exactly the same way and running into the same problem

Currently the issue updated status is updated when a comment is placed.

Status changed to closed