Issue Details (XML | Word | Printable)

Key: CWD-912
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: David O'Flynn [Atlassian]
Reporter: David O'Flynn [Atlassian]
Votes: 0
Watchers: 1
Operations

Add/Edit UI Mockup to this issue
If you were logged in you would be able to see more operations.
Crowd

Internal Directory and LDAP searches behave differently

Created: 09/Mar/08 06:38 PM   Updated: 14/Oct/08 05:44 PM   Resolved: 14/Oct/08 05:44 PM
Return to search
Component/s: Directory - LDAP
Affects Version/s: None
Fix Version/s: 1.5.1

Time Tracking:
Not Specified

Participants: David O'Flynn [Atlassian] and Shihab Hamid [Atlassian]
Since last comment: 1 year, 16 weeks, 6 days ago
Labels:


 Description  « Hide

This is most obvious in when using a Delegated Directory - the search behaviour is that of an Internal Directory, not an LDAP directory.

Options;

  • Make both behave identically
  • Make the Internal Directory search strip wildcards as we don't need them.
  • Make the different behaviour more obvious to users.

Sort Order: Ascending order - Click to sort in descending order
Donna McGahan [Atlassian] made changes - 15/Aug/08 01:16 AM
Field Original Value New Value
Component/s Directory - LDAP [ 11873 ]
[ Permalink | « Hide ]
Shihab Hamid [Atlassian] added a comment - 14/Oct/08 05:44 PM

Searches are now consistent across LDAP and Internal directories. "LIKE" searches are performed without the need for wildcards (eg. asterisks).

This was fixed by CWD-1245 and CWD-1110.


Shihab Hamid [Atlassian] made changes - 14/Oct/08 05:44 PM
Resolution Fixed [ 1 ]
Fix Version/s 1.5.1 [ 14210 ]
Status Open [ 1 ] Resolved [ 5 ]
Justin Koke [Atlassian] made changes - 11/May/09 08:31 PM
Workflow jira [ 123589 ] Feature Request Workflow [ 174405 ]
Bug tracking, issue tracking and project management software powered by Atlassian JIRA (v4.0.1#471) | Report a problem | Request a feature | Contact administrators