Project

General

Profile

Actions

Defect #25501

closed

Time entries query through multiple projects by issue custom field not possible anymore.

Added by Felix Schäfer about 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Normal
Category:
Custom fields
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

This is related to #24014

Since r15890 / #24014 it is not possible to filter time entries from different projects by an issue custom field anymore.

Sometimes it might be necessary to for example show all time entries logged against issues with a certain custom field set to some value, regardless of what project the time entry and issue are in. If one subproject is not a subproject of the other, this is not possible anymore in one query.

I can understand the concern raised in #24014, but I think restricting the global query to only issue custom fields that are "for all projects" is too restrictive. I can understand that there might be many issue custom fields, but those should only be restricted on the project time entry query, not on the global time entry query.

While researching for this I have also noticed that an issue custom field defined in a subproject will not be available anymore in the time entry query of the parent project unless the parent project also has this issue custom field defined.

I propose to show all issue custom fields (maybe limited to those active on active projects?) on the global time entry query and to show only the issue custom fields active in the current project and its subprojects on the project time entry query.

(Please note that the same problem exists on the global issue query and that it could be solved the same way)


Related issues

Related to Redmine - Defect #24014: Custom fields not used in project should not be visible in spent time reportClosedJean-Philippe Lang

Actions
Has duplicate Redmine - Defect #1662: Issue's custom fields don't appear on some filters and custom queries editorClosed2008-07-18

Actions
Actions #1

Updated by Jan from Planio www.plan.io about 7 years ago

  • Related to Defect #24014: Custom fields not used in project should not be visible in spent time report added
Actions #2

Updated by Jan from Planio www.plan.io about 7 years ago

  • Category set to Custom fields

We have recently upgraded Planio to Redmine 3.3 and we've received numerous reports within 24 hours from users criticising the removal of the custom field filters on the global time log pages. I would therefore assume that many people had been using the filters in this way previously.

Actions #3

Updated by Jean-Philippe Lang about 7 years ago

  • Target version set to 3.3.3
Actions #4

Updated by Jean-Philippe Lang about 7 years ago

  • Status changed from New to Resolved
  • Assignee set to Jean-Philippe Lang
  • Resolution set to Fixed

Fixed in r16467 for time entry and issue queries.

The following custom fields are now available:
  • for project queries: custom fields of project and its subprojects
  • for global queries: all custom fields
Actions #5

Updated by Jan from Planio www.plan.io about 7 years ago

Awesome, thanks!

Actions #6

Updated by Felix Schäfer about 7 years ago

Thanks.

Actions #7

Updated by Jean-Philippe Lang about 7 years ago

  • Status changed from Resolved to Closed
Actions #8

Updated by Toshi MARUYAMA almost 7 years ago

  • Related to Defect #1662: Issue's custom fields don't appear on some filters and custom queries editor added
Actions #9

Updated by Marius BĂLTEANU about 6 years ago

  • Related to deleted (Defect #1662: Issue's custom fields don't appear on some filters and custom queries editor)
Actions #10

Updated by Marius BĂLTEANU about 6 years ago

  • Has duplicate Defect #1662: Issue's custom fields don't appear on some filters and custom queries editor added
Actions

Also available in: Atom PDF