プロジェクト

全般

プロフィール

Vote #64234

未完了

Total-columns in the issue summary (issue_report)

Admin Redmine さんが約4年前に追加. 約4年前に更新.

ステータス:
New
優先度:
通常
担当者:
-
カテゴリ:
UI_10
対象バージョン:
-
開始日:
2022/05/09
期日:
進捗率:

0%

予定工数:
category_id:
10
version_id:
0
issue_org_id:
2281
author_id:
1565
assigned_to_id:
0
comments:
6
status_id:
1
tracker_id:
3
plus1:
0
affected_version:
closed_on:
affected_version_id:
ステータス-->[New]

説明

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!


journals

I like it. Here's a quick patch...
--------------------------------------------------------------------------------
Markus Knittig wrote:
> I like it. Here's a quick patch...

Thanks for that patch... It looks quite neat and slick. I like it... :-)
--------------------------------------------------------------------------------
What is the difference between this patch and #691 ?
--------------------------------------------------------------------------------
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!

--------------------------------------------------------------------------------

--------------------------------------------------------------------------------
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.
--------------------------------------------------------------------------------


related_issues

relates,New,691,Add column totals to Issus Summary Report

Admin Redmine さんが約4年前に更新

  • カテゴリUI_10 にセット

他の形式にエクスポート: Atom PDF

いいね!0
いいね!0