Defect #30924

Filter on Target version's Status in subproject doesn't work on version from top project

Added by Tomasz Król almost 4 years ago. Updated 8 months ago.

Status:ClosedStart date:
Priority:NormalDue date:
Assignee:Marius BALTEANU% Done:

0%

Category:Issues filter
Target version:4.1.7
Resolution:Fixed Affected version:4.0.2

Description

Hi
I'm using Redmine 4.0.2 and versions for sprints.
All versions are defined in a top project and shared with all projects.
All issues in subprojects are assigned to specific version from the top project.

When I try to filter issues in a subproject by Target version's Status - it won't work.

For example:
When adding filter "Target version's Status [is] [open]" - there are no results which is wrong.
I should get a list of issues from current project that are assigned to active versions from the Top project.

redminefilter.jpg (63.9 KB) Tomasz Król, 2019-02-26 18:22


Related issues

Related to Redmine - Feature #23215: Add the possibility to filter issues after Target Version... Closed
Duplicated by Redmine - Patch #36824: Allow to filter issues by its version status with shared ... Closed

Associated revisions

Revision 21499
Added by Marius BALTEANU 8 months ago

Allow to filter issues by its version status with shared versions (#36824, #30924).

Patch by Holger Just.

Revision 21500
Added by Go MAEDA 8 months ago

Fix RuboCop offense Style/HashSyntax (Don't mix styles in the same hash) (#36824, #30924).

Revision 21501
Added by Go MAEDA 8 months ago

Fix RuboCop offense Rails/RefuteMethods (#36824, #30924).

Revision 21504
Added by Marius BALTEANU 8 months ago

Merged r21499, r21500 and r21501 to 4.2-stable (#30924).

Revision 21505
Added by Marius BALTEANU 8 months ago

Merged r21499, r21500 and r21501 to 4.1-stable (#30924).

History

#1 Updated by Mitsuyoshi Kawabata over 1 year ago

+1

#2 Updated by Go MAEDA over 1 year ago

  • Status changed from New to Confirmed

I have confirmed the issue.

Steps to reproduce:

1. Create a project. Then, create a subproject of the project
2. Create a version in the parent project. Set the version's "Sharing" setting to "With all projects"
3. Create an issue in the subproject
4. Set the target version of the issue to the version created in step 2
5. Apply the filter [Target version's Status] [is] [open]

Expected behavior:
The issue created in step 4 should be displayed in the issues list.

Actual behavior:
No issue is displayed in the issues list.

Not only "Target version's Status" filter but also "Target version's Due date" filter does not work for issues which target version is one of the ancestors' shared version.

#3 Updated by Go MAEDA over 1 year ago

  • Related to Feature #23215: Add the possibility to filter issues after Target Version's Status and Due Date added

#4 Updated by Marius BALTEANU 9 months ago

  • Target version set to Candidate for next minor release

#5 Updated by Holger Just 9 months ago

  • Related to Patch #36824: Allow to filter issues by its version status with shared versions added

#6 Updated by Marius BALTEANU 8 months ago

  • Status changed from Confirmed to Resolved
  • Assignee set to Marius BALTEANU
  • Target version changed from Candidate for next minor release to 4.1.7
  • Resolution set to Fixed

#7 Updated by Marius BALTEANU 8 months ago

  • Related to deleted (Patch #36824: Allow to filter issues by its version status with shared versions)

#8 Updated by Marius BALTEANU 8 months ago

  • Duplicated by Patch #36824: Allow to filter issues by its version status with shared versions added

#9 Updated by Marius BALTEANU 8 months ago

Fixed in r21499.

#10 Updated by Marius BALTEANU 8 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF