Project

General

Profile

Actions

Feature #30808

closed

Multiple issue ids in "Subtasks" filter

Feature #30808: Multiple issue ids in "Subtasks" filter

Added by Hirofumi Kadoya almost 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Issues filter
Target version:
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--


Files

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

Related issues 1 (0 open — 1 closed)

Related to Redmine - Feature #30482: Multiple issue ids in "Parent task" filterClosedGo MAEDAActions

Updated by Go MAEDA almost 8 years ago Actions #1

  • Tracker changed from Defect to Feature

Updated by Go MAEDA almost 8 years ago Actions #2

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

Updated by Go MAEDA almost 8 years ago Actions #3

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

Updated by Yuichi HARADA over 7 years ago Actions #4

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

Updated by Go MAEDA over 7 years ago Actions #5

  • Target version set to Candidate for next major release

Updated by Go MAEDA over 7 years ago Actions #6

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

Actions

Also available in: PDF Atom