Custom Fields vs Spent Time Reports

Added by Mischa The Evil about 9 years ago

Hi there,

I took the liberty to open-up this discussion-thread to further discuss the issues #1692 and #1766 in one central place instead of discussing it on the issue's notes.

Introduction:

Spent Time entries are "reported" at two places:
  1. Spent Time "Details"-report @ /projects/foo/timelog/details
  2. Spent Time "Report"-report @ /projects/foo/timelog/report

Issues:

Now, concerning both issues:

Issue #1692: (Patch: Enable time-tracking additional fields in reports filters)
This issue actually should be "in the feature tracker". For what I've understood from it is that it is a request to show timelog.custom_fields as filters in the Spent Time "Report"-report @ /projects/foo/timelog/report.
J-PL has already commented the following on that issue:

Actually, boolean and list timelogs custom fields are available in the time report (eg. /projects/foo/timelog/report)

As visibly marked in the 2nd screenshot (of the Spent Time "Report"-report) I can confirm that timelog.custom_fields of the types list and boolean are indeed already available as filters in the Spent Time "Report"-report @ /projects/foo/timelog/report. See "review" for a more indepth description.

Issue #1766: (Feature: Timelog custom-field columns should become addable to 'Spent Time'-details report.)
I have created this feature-request due to the fact that I was missing timelog.custom_fields in the "Report"-report @ /projects/foo/timelog/details.
At the moment the only showed columns are:
  • Date
  • Member
  • Activity
  • Project
  • Issue
  • Comment
  • Hours

This issue is regarding the thing that it would be great to be able to create a possibility to explicitally mark available timelog.custom_fields to be displayed in the "Report"-report @ /projects/foo/timelog/details also besides the already available columns.
I have filed another feature-request (#1767: "Make custom-fields (timelog and project) configurable/switchable per project") too. As the title says already it requests the ability to configure/switch the available timelog.custom_fields per project just like that that is already implemented for issue.custom_fields.

Review:

I've done some researching (yeah, I already said that I like to do that...) on the timelog-reports in a more broad sense.

To be precise I've created 28 custom_fields. 7 of all the respective types of issue.custom_fields, 7 of all the respective types of timelog.custom_fields, 7 of all the respective types of project.custom_fields and 7 of all the respective types of user.custom_fields. I named them accordingly of their type and the sort of custom_field (issue, timelog, etc.).
Note though that in this situation both project.custom_fields and user.custom_fields are irrelevant imho.

Here are the relevant screens:
  • Issue.custom_fields
  • Timelog.custom_fields
  • Project.custom_fields
  • User.custom_fields

Now I've made sure that at least for one issue all the respective fields are filled. I did the same for some spent time-entries.

Now I switched to the timelog reports and interpreted the screens (see "Introduction") from which I took notes in a textfile. I'll post the results here in pre-mode:

                TIMELOG-REPORTS VS CUSTOM FIELDS

---------------------------------------------------------
                | Timelog (details) |                   | @ /projects/foo/timelog/details
                |                   | Timelog (report)  | @ /projects/foo/timelog/report
---------------------------------------------------------
Issue.custom_fields
- Text          |                   | C4                |
- Long Text     |                   | C4                |
- Integer       |                   | C4                |
- Float         |                   | C4                |
- List          |                   | F                 |
- Date          |                   | C4                |
- Boolean       |                   | F                 |
---------------------------------------------------------
Timelog.custom_fields
- Text          | R                 | C3                |
- Long Text     | R                 | C3                |
- Integer       | R                 | C3                |
- Float         | R                 | C3                |
- List          | R                 | F+                |
- Date          | R                 | C3                |
- Boolean       | R                 | F+                |
---------------------------------------------------------
Project.custom_fields
- Text          |                   |                   |
- Long Text     |                   |                   |
- Integer       |                   |                   |
- Float         |                   |                   |
- List          |                   |                   |
- Date          |                   |                   |
- Boolean       |                   |                   |
---------------------------------------------------------
User.custom_fields
- Text          |                   |                   |
- Long Text     |                   |                   |
- Integer       |                   |                   |
- Float         |                   |                   |
- List          |                   |                   |
- Date          |                   |                   |
- Boolean       |                   |                   |
---------------------------------------------------------

R  = request of #1766: (configurable) visible Columns on the "details" report.
F  = available as Filter on the "report" report.
F+ = available as Filter on the "report" report.
     (what J-PL describes @ http://www.redmine.org/issues/show/1692#note-2)
C3 = see conclusion no. 3
C4 = see conclusion no. 4

My conclusions this far:

  1. Issues #1692 and #1766 are both related to each other.
  2. Though issue #1766 is not actually a duplicate of #1692 since it is related to another timelog-report ("'Spent Time'-details" report) and describes columns instead of filters (which are used on their turn on the "'Spent Time'-report" report).
  3. From what I understand from #1692: more timelog.custom_field-types (like Integer, Float, Date, etc) filters should become available on the "'Spent Time'-report" report.
  4. Question after (3): Should issue #1692 also count as a request to also make more issue.custom_field-types (like Integer, Float, Date, etc) filters available on the "'Spent Time'-report" report (see C4 in my matrix-thingy :-)?

I'd like to see more comments about these issues to make sure both issues are handled correctly and (if it is decided so by lead) implemented as issued.

Greetings,

Mischa.

Replies (4)

RE: Custom Fields vs Spent Time Reports - Added by Bob Pack almost 5 years ago

I am not getting the stated behavior, using Redmine 2.1.2. According to your matrix, Issue custom fields should be filterable on the Spent Time Reports. I have two issue custom fields that aren't appearing as filter items for Spent Time Reports, and both are List-type (not even multiple, just simple list type). I have seen that Spent Time Custom Fields of list type DO show up, but in my observation, NOT the issue custom fields.

issue-custom-fields.png - Two issue custom fields that should be filterable by your description (14 KB)

spent-time-filter-list.png - The two fields clearly aren't showing up in the report filter (15.8 KB)

RE: Custom Fields vs Spent Time Reports - Added by Mischa The Evil almost 5 years ago

Bob Pack wrote:

I am not getting the stated behavior, using Redmine 2.1.2. According to your matrix, Issue custom fields should be filterable on the Spent Time Reports. I have two issue custom fields that aren't appearing as filter items for Spent Time Reports, and both are List-type (not even multiple, just simple list type). I have seen that Spent Time Custom Fields of list type DO show up, but in my observation, NOT the issue custom fields.

I've taken a quick look on *.m.redmine.org (running 2.1.0.stable) and noticed that you are indeed right. Though, do remember that this post is over 4 years old and covered Redmine 0.7.x-0.8.x. I'm not sure if this is actually a regression that has taken place somewhere between or an incorrect observation on my side at that time.

Please open a specific feature request if this is needed.

Greets,

Mischa.

RE: Custom Fields vs Spent Time Reports - Added by Mischa The Evil almost 5 years ago

Mischa The Evil wrote:

Bob Pack wrote:

I am not getting the stated behavior, using Redmine 2.1.2. [...]

I've taken a quick look on *.m.redmine.org (running 2.1.0.stable) and noticed that you are indeed right. Though, do remember that this post is over 4 years old and covered Redmine 0.7.x-0.8.x. I'm not sure if this is actually a regression that has taken place somewhere between or an incorrect observation on my side at that time.

Please open a specific feature request if this is needed.

FTR: see the recent activity for #1766. This is being implemented into Redmine 2.3.0.

RE: Custom Fields vs Spent Time Reports - Added by Bob Pack almost 5 years ago

That is great! I think this is a huge step forward. I am hoping to have the time to contribute to this great project eventually. Ruby/Rails is not my strong suit, but I am sure I'll find some different ways... just too busy right now. Thanks Mischa.

(1-4/4)