Patch #26091

Allow to filter by any visible version on the global issues view

Added by Holger Just 3 months ago. Updated about 1 month ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:Issues filter
Target version:4.1.0

Description

Currently, the global issues view only allows to filter by system-shared versions but not e.g. for versions shared to some projects or not stared at all.

Since the global issue view is often used as a quick filter to check what is happening in all projects, filtering by any visible version would allow to drill down from there instead of having to first select the correct parent project and then starting the filter there. Also, with saved shared queries, a common starting point is the global issue view instead of individual projects.

The attached patch removes the restriction to only allow filtering by system-shared versions. Instead, it allows filtering by any version visible to the current user.

0001-Allow-to-filter-by-all-versions-on-the-global-issue-.patch Magnifier (829 Bytes) Holger Just, 2017-06-02 17:52


Related issues

Related to Redmine - Defect #26023: Category filter only shows categories of current project New

History

#1 Updated by Mischa The Evil 2 months ago

  • Target version set to Unplanned

I find this a nice addition indeed. Setting target to unplanned.

#2 Updated by Holger Just 2 months ago

As for the rationale, this patch implements the same behavior as for custom fields (in #25501) and for categories (in #26023).

#3 Updated by Go MAEDA 2 months ago

The proposed behavior is also consistent with #24769 (user type custom field).

#4 Updated by Go MAEDA 2 months ago

Mischa The Evil wrote:

I find this a nice addition indeed. Setting target to unplanned.

I think we can merge this patch right now. Mischa, what do you think about setting target version to 3.4.0? Is it OK with you?

#5 Updated by Marius BALTEANU 2 months ago

Go MAEDA wrote:

Mischa The Evil wrote:

I find this a nice addition indeed. Setting target to unplanned.

I think we can merge this patch right now. Mischa, what do you think about setting target version to 3.4.0? Is it OK with you?

My two cents:
I'm in favor to set the version:3.5.0 in order to have the 3.4.0 released as soon as possible.

#6 Updated by Robert Schneider 2 months ago

My two cents:
I'm in favor to set the version:3.5.0 in order to have the 3.4.0 released as soon as possible.

Oh, yes please! Good idea. 3.4.0 matured enough. I have started a discussion about that Why don't you just release 3.4.0? since we are waiting so long now.

My two cents. Total now: 4 cents ;-)

#7 Updated by Holger Just 2 months ago

Not to spoil anything here, but this patch here won't result in any delay in getting 3.4.0 released. It is a tiny patch which helps resolve (together with #24769, #25501 and #26023) some inconsistencies in the way the global filters work. It takes about 5 minutes of work to merge (and backport) this and several of the other already assigned patches.

In general, there's no gain from having tiny patches wait for the next release. Instead, the release is (probably) only delayed by the larger open issues which still take some thinking, or review plus whatever JPL already has in his sleeves.

#8 Updated by Robert Schneider 2 months ago

Holger, I'm happy about any new Redmine feature! If it's really such a small task applying that patch, then they should do it. I'm just a bit afraid that there is actually more to do. Already the communication here has to be done, thinking about it, creating a test, ... There should be a point where new things get added to the next version, otherwise 3.4.0 might be released next year ;-) Now I shut up.

#9 Updated by Go MAEDA about 1 month ago

  • Category set to Issues filter

#10 Updated by Toshi MARUYAMA about 1 month ago

  • Related to Defect #26023: Category filter only shows categories of current project added

#11 Updated by Go MAEDA about 1 month ago

  • Target version changed from Unplanned to 4.1.0

As mentioned in #26091#note-2 and #26091#note-3, the behaviour of this patch is consistent with #25501 and #24769. They were already delivered in 3.4.0.

I am setting target version to 4.1.0.

Also available in: Atom PDF