Project

General

Profile

Actions

Defect #5885

closed

Issue with Filters

Added by Mario Scondo about 14 years ago. Updated about 14 years ago.

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

0%

Estimated time:
Resolution:
Invalid
Affected version:

Description

Hello,

I did realize a problem when trying to filter for issues. A sample installation with two posted issues XXXXXX

These are the steps to reproduce the behaviour as described above:
- login by utilizing an user that is configured to use the role 'manager'
- click on 'My Page'
- click on 'View all issues'
- Configue the filter settings:
o old: status=all, author=is me
o new: status=is new, author=is me
- click on 'apply'
- the next page is blank (the item list of fetched issues is empty and there
are no controls availablt to refine the search. Just the header and the side
bar are available)

System Configuration:
---------------------
- configure Redmine to use MySQL 5.1
- Linux Distribution: Ubuntu 10.04, x86-64
- Redmine SVN Branch 0.9
o no additional plugin's have been installed!
o Redmine is running in 'production' mode
- After initialization of the database the migration of
issues from a Mantis v1.x installation has been performed without
any error messages. Utilized encoding: ISO 8859-15)

I did install Redmine from the following SVN branch:
---
URL: http://redmine.rubyforge.org/svn/branches/0.9-stable
Repository Root: http://redmine.rubyforge.org/svn
Repository UUID: e93f8b46-1217-0410-a6f0-8f06a7374b81
Revision: 3840

Actions #1

Updated by Mario Scondo about 14 years ago

I'm sorry. The string 'XXXXX' in the description has to be replaced be the following problem description:

-> When trying to filter issues with the criteria 'is New' the resulting page is empty.
Actions #2

Updated by Felix Schäfer about 14 years ago

The rails MySQL adapter is currently not compatible with MySQL 5.1, please downgrade your MySQL installation and see if the problem persists.

Actions #3

Updated by Mario Scondo about 14 years ago

Are there any known problems with Postgres 8.3 and 8.4?

Actions #4

Updated by Felix Schäfer about 14 years ago

Holger Just on IRC:

pg 8.3 works well. 8.4 should work fine with trunk at least

Actions #5

Updated by Felix Schäfer about 14 years ago

But now that I thought of it a little, I think this is a problem fixed in trunk, but for which the fix has not been backported to 0.9. Have you tried searching for a similar issue here?

Actions #6

Updated by Mario Scondo about 14 years ago

I did not find issues related to 'filtering'.

While trying to migrate datasets from Mantis to Postgres 8.4 the script is failing... However, I think I have to install MySQL 5.0 to solve the problem.

Actions #7

Updated by Mario Scondo about 14 years ago

I did try to perform the migration and do the filtering with a MySQL 5.0.x backend and I was successful.

Thank you for your help.

Actions #8

Updated by Mario Scondo about 14 years ago

  • Status changed from New to Resolved
Actions #9

Updated by Felix Schäfer about 14 years ago

  • Status changed from Resolved to Closed
  • Resolution set to Invalid

Happy to help :-)

Actions

Also available in: Atom PDF