directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean-Marie Damas (JIRA)" <>
Subject [jira] [Commented] (DIRSTUDIO-946) Add the ability of saving common attributes list
Date Mon, 09 Sep 2013 07:24:56 GMT


Jean-Marie Damas commented on DIRSTUDIO-946:

That's not my use case. I'm a *developer*, not an admin. I use Apache DS to validate and test
LDAP requests that will be executed with Talend (open source) tools in a batch execution environment.

Because it's about the same search, in term of business or functionality, but since I'm in
development phase, I use only *one* search request at a time but with many combinations of
attributes, adding and/or removing some of then, according to my development needs.
So it would be easier for me to have a GUI to see all of them and manage their consistency
with more powerful mechanisms (save/load) than the actual small dropdown list.

With the solution of different searches, I would have to name the search with the attributes
names (and I use plenty of them), witch is not useful.

Certainly my usage is a bit unusual ?
> Add the ability of saving common attributes list
> ------------------------------------------------
>                 Key: DIRSTUDIO-946
>                 URL:
>             Project: Directory Studio
>          Issue Type: Improvement
>          Components: studio-ldapbrowser
>    Affects Versions: 2.0.0-M8 (2.0.0.v20130628)
>            Reporter: Jean-Marie Damas
>            Priority: Minor
>              Labels: filter, load, save, search
>         Attachments: ADS_SearchGUI.jpg, SOFTERRA_SearchGUI.jpg
> In search GUI (and certainly in others screens), it would be useful to be able to save
(and so, further, reload) the commonly used attributes list.
> The actual drop-down list stores the precedent used lists but it isn't so easy to use.
> For example, by creating an Attribute List Editor with buttons "Save" and "Load" ?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message