Project

General

Profile

Defect #1326

ref_issues with custom fields not working

Added by Daniel Wagner about 5 years ago. Updated almost 4 years ago.

Status:
終了(Closed)
Priority:
通常(Normal)
Category:
-
Target version:
-
Start date:
05/22/2014
Due date:
% Done:

0%

Estimated time:

Description

Hello,

if I specify a custom field filter as follows {{ref_issues(-p=project,-f:cf_6=REQ_001)}}, I get attached error message. I've already checked that the custom field Id I want to use is 6 for sure.


Files

picture486-1.png (2.66 KB) picture486-1.png Daniel Wagner, 05/22/2014 10:23 PM

Related issues

Related to Wiki Lists - Defect #1386: failed add_filter parent_id終了(Closed)07/09/2015

Actions

History

#1

Updated by Tomohisa Kusukawa about 5 years ago

  • Status changed from 新規(New) to フィードバック(Reopend)
  • Assignee set to Daniel Wagner
  • Target version set to 0.0.4

I'm sorry reply too late.

I found that custom field filtering works with the custom query.

e.g.

{{ref_issues(-i=2,-f:cf_3=hoge)}}

"2": custom query id.
You can check this ID in the URL when you select a custom query.

"3": custom field id.
You can check the ID in the URL of the Administration page of custom fields.

#2

Updated by Tomohisa Kusukawa about 5 years ago

  • Target version deleted (0.0.4)
#3

Updated by Daniel Wagner about 5 years ago

Hi,

I tested the workaround with -i option and using a custom query, which medicore success - it doesn't work reliable here.

But I found out that if in the settings of the custom field the checkbox "for all projects" is active, then it ref_issues works as documented, i.e. I can use

{{ref_issues(-p=toolbox,-f:cf_6=bla)}}

If the checkbox isn't active, and the custom field is activated for individual projects then it doesn't work.

#4

Updated by Daniel Wagner about 5 years ago

I found out that ref_issues with -f and custom fields works in combination with -i, when the specified custom query is project specific and not marked as "For all projects".

#5

Updated by Tomohisa Kusukawa about 5 years ago

I'm sorry for my insufficient description.

Did this resolve the issue?

#6

Updated by Alexandre AlxChS almost 5 years ago

I can't understand. Is this not works?

{{ref_issues(-s=sorting,subject,assigned_to,status,-f:parent_id=24127)}}

Redmine Shows:

#7

Updated by Tomohisa Kusukawa almost 5 years ago

  • Assignee changed from Daniel Wagner to Tomohisa Kusukawa

parent_id can not be used as a filter.

The following seems to be available as a filtere in redmine2.5.2.

status_id, project_id, tracker_id, priority_id, author_id,
assigned_to_id, assigned_to_role, subject, created_on, updated_on,
closed_on, start_date, due_date, estimated_hours, done_ratio,
is_private, watcher_id, relates, duplicates, duplicated,
blocks, blocked, precedes, follows, copied_to,
copied_from, description, subjectdescription

#8

Updated by Tomohisa Kusukawa almost 4 years ago

  • Related to Defect #1386: failed add_filter parent_id added
#9

Updated by Tomohisa Kusukawa almost 4 years ago

  • Status changed from フィードバック(Reopend) to 終了(Closed)

Also available in: Atom PDF