Project

General

Profile

Actions

Feature #13298

closed

Grouping issue history (activity) in issue history tabs

Added by Pavel Lautsevich over 11 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Duplicate

Description

It would be very useful if the activity on the task grouped by type: comments, status changes and etc., like in the Jira.


Files

task-activity-grouping.png (9.24 KB) task-activity-grouping.png Pavel Lautsevich, 2013-02-26 19:40

Related issues

Is duplicate of Redmine - Feature #3058: Show issue history using tabsClosedJean-Philippe Lang2009-03-26

Actions
Actions #1

Updated by Jan Niggemann (redmine.org team member) over 11 years ago

I like it the way it is because you have everything on a consistent timeline.
With your solution, I have to switch back and forth between, say, comments and status changes to know in which order they took place...

Actions #2

Updated by Pavel Lautsevich over 11 years ago

The system must remember the user's choice and display the corresponding tab.

Actions #3

Updated by Toshi MARUYAMA over 11 years ago

  • Category changed from UI to Activity view
Actions #4

Updated by Mischa The Evil over 11 years ago

  • Subject changed from Grouping task activity log to Grouping issue history (activity) in issue history tabs
  • Category changed from Activity view to Issues

Toshi MARUYAMA wrote:

  • Category changed from UI to Activity view

This request is not about the activity view (it is actually about source:/trunk/app/views/issues/_history.html.erb).
Looking at the screenshot Pavel is requesting a way to display the (Redmine) issue history (aka issue notes aka issue comments) like it is done in Jira where the issue activity is displayed divided over several tabs (see e.g. https://confluence.atlassian.com/display/JIRA052/Viewing+an+Issue's+Change+History).
An old plugin, Redmine Issue History Tabs Plugin, implemented something a bit similar, but divided the issue history (aka ...) over only two tabs: All and Comments. I noticed that some 2.x compatible forks seem to exist on GitHub though nowadays.

Jan Niggemann wrote:

I like it the way it is because you have everything on a consistent timeline.
With your solution, I have to switch back and forth between, say, comments and status changes to know in which order they took place...

That shouldn't be a problem with such feature, I think. That case should be covered by the/an All tab which needs to show all issue history in the order in which it took place (like as it is now also the default in Redmine).

Actions #5

Updated by Mischa The Evil over 11 years ago

  • Description updated (diff)

Adjusting width of screenshot.

Actions #6

Updated by Jan Niggemann (redmine.org team member) over 11 years ago

Mischa The Evil wrote:

Jan Niggemann wrote:

I like it the way it is because you have everything on a consistent timeline.
With your solution, I have to switch back and forth between, say, comments and status changes to know in which order they took place...

That shouldn't be a problem with such feature, I think. That case should be covered by the/an All tab which needs to show all issue history in the order in which it took place (like as it is now also the default in Redmine).

I don't know JIRA but with an All tab it's OK for me...

Actions #7

Updated by Pavel Lautsevich over 11 years ago

This is exactly what I need! http://www.redmine.org/plugins/redmine_issue_detailed_tabs_time

But there are no guarantees on the term support of the solution, so I need directly from a box! Please!

Actions #8

Updated by mark kalender over 11 years ago

redmine_issue_detailed_tabs_time v 0.0.7 was done this weekend.
it now hides tabs if there is no activity for it. not sure if this is a desired effect.
it felt to clutered when an issue does not have much action on it.

Also im not sure about remembering user tab selection for next time it loads, but at the moment it always defaults to "All" tab. and the tabs only appear if something to put there

Actions #9

Updated by Pavel Lautsevich over 11 years ago

Mark, thak you 4 your work. If I understand correctly, there is a chance to include your implementation in the main package Redmine. http://www.redmine.org/boards/3/topics/36787?r=36809#message-36809 Is this true?

Actions #10

Updated by mark kalender over 11 years ago

Pavel Lautsevich wrote:

Mark, thak you 4 your work. If I understand correctly, there is a chance to include your implementation in the main package Redmine. http://www.redmine.org/boards/3/topics/36787?r=36809#message-36809 Is this true?

Hey Pavel, ill have to look into it, ruby is very new to me but the changes are so simple its a great stepping stone for me to learn the language. Daniel or others would have to really vote this up for me to look into it.

in the mean time, be assured im a software engineer with a growing team, went from 2 ppl to 8 ppl so far in the last year, so having a good project management/Agile system is essential to me. my plugin and a few other plugins that im trying to make are very essential to our company usability over jirra and i believe in open source and welcome others to help better the plugins for you guys and our team. so as long as our team is here, i will keep these plugin growing and even re-fork old plugins that i find useful to streamlining our work here

Actions #11

Updated by Pavel Lautsevich over 11 years ago

Mark thank you and good luck! =)

Actions #12

Updated by Toshi MARUYAMA about 11 years ago

  • Related to Feature #8536: Separate notes/comments from issue updates added
Actions #13

Updated by Go MAEDA over 6 years ago

  • Related to deleted (Feature #8536: Separate notes/comments from issue updates)
Actions #14

Updated by Go MAEDA over 6 years ago

  • Is duplicate of Feature #3058: Show issue history using tabs added
Actions #15

Updated by Go MAEDA over 6 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

A patch to implement the same feature was submitted in #3058.

Actions

Also available in: Atom PDF