Project

General

Profile

Actions

Defect #6871

closed

members missing from assigned to filter

Added by Paul Wilson over 13 years ago. Updated about 11 years ago.

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

0%

Estimated time:
Resolution:
Fixed
Affected version:

Description

Two related issues to report:

This example project has 16 member associated with it:

The first time landing on the Issues in a project, I choose the option to add a filter and select "Assigned to"
All available members appear in the drop-down list and can be selected but after selecting a member and applying the filter, the drop-down no longer includes all available members. Only 12 area available.

While still on the Issues page, I clear the filters and again opt to add a filter and select "Assigned to"
This time all available members do not appear in the drop-down list. Only 15 are listed. After selecting a member and applying the filter, the drop-down again includes only 12 members.

O/S: Linux (SLES 10 SP 1)
Redmine version: 1.0.1.stable.4033
MySQL Server version: 5.0.51a-community-log MySQL Community Edition
Ruby version: 1.8.6 (x86_64-linux)
RubyGems Version: 1.3.6
Rack Version: 1.0
Rails Version: 2.3.5

Issue validated as still existing in Redmine 1.0.3.stable.4390

Actions #1

Updated by Jean-Philippe Lang over 13 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

See #6521.

Actions #2

Updated by Jean-Philippe Lang over 13 years ago

  • Status changed from Closed to New
  • Resolution deleted (Duplicate)

Sorry.

Actions #3

Updated by Daniel Felix about 11 years ago

  • Due date set to 2013-01-22
  • Status changed from New to Needs feedback

I'm not able to reproduce this with Redmine 2.2.1 and trunk.

This seems to be fixed.

Any news on this? If there is no Feedback, I'm going to close this issue next week.
Reasons for closing: Issue age and affected redmine version.

Actions #4

Updated by Daniel Felix about 11 years ago

  • Affected version (unused) set to 1.0.3
  • Affected version set to 1.0.3
Actions #5

Updated by Paul Wilson about 11 years ago

I am fine with closing this issue. In testing on my current version, (2.0.4,) this is no longer a problem.

Actions #6

Updated by Daniel Felix about 11 years ago

  • Due date deleted (2013-01-22)
  • Status changed from Needs feedback to Closed
  • Resolution set to Fixed

Hi Paul,

thanks for your quick feedback!

Closed.

Actions

Also available in: Atom PDF