Project

General

Profile

Actions

Defect #9738

closed

Setting of cross-project custom query is not remembered inside project

Added by James Berry over 12 years ago. Updated over 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Issues
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

In previous versions of Redmine, a custom query was remembered when I returned to the issues tab. After I upgraded our redmine to the latest HEAD, this is no longer the case.

Steps to Reproduce:

  1. Go to the Issues tab
  2. Click on a custom query
  3. Note that the organization of the issues has changed (ordering, grouping, etc.)
  4. Click again on the Issues tab
  5. Unexpected: note that the custom query is lost

Now:

  1. Go to the Issues tab
  2. Click on a custom query
  3. Note that the organization of the issues has changed (ordering, grouping, etc.)
  4. Click on the "Apply" button
  5. Click again on the Issues tab
  6. Note that the organization of the issues has not changed.

Expected Result:

  • It should not be necessary to click "Apply" for the custom query to be recognized.

This seems to work properly on the redmine site running 1.2.2, but it doesn't work for me on my installation running on trunk HEAD.


Related issues

Related to Redmine - Defect #9108: Custom query not saving status filterClosedEtienne Massip2011-08-23

Actions
Has duplicate Redmine - Defect #9742: Issues from other projects appearing in an specific projectClosed

Actions
Actions

Also available in: Atom PDF