I'm looking for a part-time remote job.

Hire me


I'm the author of:

Mastering Redmine is a comprehensive guide with tips, tricks and best practices, and an easy-to-learn structure.

Check the book's project or

Buy the book

Social pages of the book:

By buying this book you also donate to Redmine (see this page).


Follow me:

Improvement #862

Support user first and last name in requests

Added by Andriy Lesyuk about 9 years ago. Updated over 8 years ago.

Status:
Open
Priority:
Minor
Assignee:
Category:
Core
Target version:
Start date:
Due date:
% Done:

0%


Description

Right now if you need to specidy user for some context you need to enter the username or Jabber ID... This is not very friendly...

The idea is to support queries like:

User: Assign to Andriy Lesyuk
User: Assign to Kostyantyn
User: Assign to Sergiy F.
User: Assign to Dmytriv

The algorithm should be smart enough to determine who is this user... For example, if user tells “Andriy” Orangutan should claim that there are many Andriy’s. If user tells “Kostyantyn” Orangutan should use Kostyantyn Kornienko because he is the only Kostyantyn etc.


Related issues

Related to Orangutan - Enhancement #960: Support for non-LDAP usernames Closed 22 Jan 2011 24 Feb 2011

History

#1 Updated by Andriy Lesyuk about 9 years ago

I guess this can be done using filter...

#2 Updated by Andriy Lesyuk almost 9 years ago

On same_login setups this issue becomes more important because user can specify the following:
  • jabber username or jabber id (this will be default);
  • first name and/or last name;
  • redmine login (currently unsupported).

#3 Updated by Andriy Lesyuk almost 9 years ago

  • Target version set to 1.08

#4 Updated by Andriy Lesyuk almost 9 years ago

  • Target version changed from 1.08 to 2.00

#5 Updated by Andriy Lesyuk over 8 years ago

  • Tracker changed from Feature to Improvement

Also available in: Atom PDF

Terms of use | Privacy policy