Feature #30808

Multiple issue ids in "Subtasks" filter

Added by Hirofumi Kadoya 8 months ago. Updated 8 months ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:Go MAEDA% Done:

0%

Category:Issues filter
Target version:4.1.0
Resolution:Fixed

Description

at Custom Query
child task can select single
issue can select multiple

I'd like to select mulutiple likely issue

about parent task
http://www.redmine.org/issues/30482

---ja start---
カスタムクエリにて
抽出条件をチケットにすると、カンマ区切りで複数チケットを設定できるが
子チケットでは複数指定ができないです

親チケットがだめだったから子チケットもだめだろうと思ったら
やっぱりだめでした

--ja end--

30808-fix-child-id-filter.patch Magnifier (1.56 KB) Yuichi HARADA, 2019-02-19 03:14


Related issues

Related to Redmine - Feature #30482: Multiple issue ids in "Parent task" filter Closed

Associated revisions

Revision 17908
Added by Go MAEDA 8 months ago

Multiple issue ids in "Subtasks" filter (#30808).

Patch by Yuichi HARADA.

History

#1 Updated by Go MAEDA 8 months ago

  • Tracker changed from Defect to Feature

#2 Updated by Go MAEDA 8 months ago

  • Related to Feature #30482: Multiple issue ids in "Parent task" filter added

#3 Updated by Go MAEDA 8 months ago

  • Subject changed from Multiple issue ids in "child task" filter to Multiple issue ids in "Subtasks" filter

I am trying to explain the request that partially written in Japanese.

"Subtasks" issues filter should support comma-separated multiple issue ids as already supported in "Issues" and "Parent task" filter.

In the current trunk r17862, there are three issues filters that accept issue id. "Issue" and "Parent task" filter accepts comma-separated issue ids as a parameter for "is (=)" operator but only "Subtasks" filter does not.

#4 Updated by Yuichi HARADA 8 months ago

I changed so that The Subtasks filter supports comma-separated multiple issue ids.
I attached a patch.

#5 Updated by Go MAEDA 8 months ago

  • Target version set to Candidate for next major release

#6 Updated by Go MAEDA 8 months ago

  • Status changed from New to Closed
  • Assignee set to Go MAEDA
  • Target version changed from Candidate for next major release to 4.1.0
  • Resolution set to Fixed

Committed the patch. Thank you for your contribution.

Also available in: Atom PDF