Project

General

Profile

Actions

Patch #2281

closed

Total-columns in the issue summary (issue_report)

Added by Mischa The Evil almost 16 years ago. Updated 30 days ago.

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

0%

Estimated time:

Description

I was just wondering if it would be useful to have total-columns inside the issue summary (issue_report) and the related issue_report detail-views.

Such a functionality would, for example, make it easier to look-up:
  • how many issues are open/closed which are targetted to any version.
  • how many issues are open/closed in general (cross-tracker, thus the total number of issues on a project)
  • resulting of the above; make it easy to see how many non-versioned issues exists.

An example of what I'm talking about could look like:


Files

issues_report-mod-new.jpg (41.2 KB) issues_report-mod-new.jpg Mischa The Evil, 2008-12-05 17:45
total_columns.diff (1.95 KB) total_columns.diff Patch from the current git master Markus Knittig, 2008-12-05 22:06

Related issues

Related to Redmine - Feature #691: Add column totals to Issues Summary ReportClosedGo MAEDA2008-02-19

Actions
Actions #1

Updated by Markus Knittig almost 16 years ago

I like it. Here's a quick patch...

Actions #2

Updated by Mischa The Evil almost 16 years ago

Markus Knittig wrote:

I like it. Here's a quick patch...

Thanks for that patch... It looks quite neat and slick. I like it... :-)

Actions #3

Updated by Ewan Makepeace almost 16 years ago

What is the difference between this patch and #691 ?

Actions #4

Updated by Mischa The Evil almost 16 years ago

Ewan Makepeace wrote:

What is the difference between this patch and #691 ?

Almost identical. The patch from #691 also provides links on the totals which redirects to the issuelist with the required filters applied. This isn't something I use/require...
AFAICT this patch by Markus Knittig seems a bit more clean without hard-coded strings and so on...

I didn't found #691 before opening this issue... I'll relate them since they both implement it slightly different...

Good eye!

Actions #5

Updated by Mischa The Evil over 15 years ago

  • Tracker changed from Feature to Patch
Actions #6

Updated by Anonymous almost 6 years ago

It could be a penalty to performance if there are too many versions, too many categories and etc as it introduces additional for loops. This IMHO would be a lot cheaper to do on the front end instead, but it would require correct classification of columns containing numbers.

P.S. possibly this ticket not really related to UI.

Actions #7

Updated by Go MAEDA 30 days ago

  • Status changed from New to Closed

Implemented in r23163.

Actions

Also available in: Atom PDF