Patch #2281

Total-columns in the issue summary (issue_report)

Added by Mischa The Evil about 11 years ago. Updated 12 months ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:UI
Target version:-

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:

issues_report-mod-new.jpg (41.2 KB) Mischa The Evil, 2008-12-05 17:45

total_columns.diff Magnifier - Patch from the current git master (1.95 KB) Markus Knittig, 2008-12-05 22:06


Related issues

Related to Redmine - Patch #691: Add column totals to Issus Summary Report New 2008-02-19

History

#1 Updated by Markus Knittig about 11 years ago

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

#2 Updated by Mischa The Evil about 11 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... :-)

#3 Updated by Ewan Makepeace about 11 years ago

What is the difference between this patch and #691 ?

#4 Updated by Mischa The Evil about 11 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!

#5 Updated by Mischa The Evil almost 11 years ago

  • Tracker changed from Feature to Patch

#6 Updated by Anonymous 12 months 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.

Also available in: Atom PDF