directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Seelmann (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DIRSTUDIO-638) Improve the way we ask for operational attrbutes
Date Fri, 26 Mar 2010 15:00:28 GMT

     [ https://issues.apache.org/jira/browse/DIRSTUDIO-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stefan Seelmann updated DIRSTUDIO-638:
--------------------------------------

    Component/s: studio-ldapbrowser
        Summary: Improve the way we ask for operational attrbutes  (was: Improve the wy we
ask for operational attrbutes)

I'd propose to remove all those filter actions in the entry editor preferences:
- show object class attribute
- show must attributes
- show may attributes

We have a more powerful feature to filter the attributes in the entry editor, the quick filter.


> Improve the way we ask for operational attrbutes
> ------------------------------------------------
>
>                 Key: DIRSTUDIO-638
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-638
>             Project: Directory Studio
>          Issue Type: Improvement
>          Components: studio-ldapbrowser
>    Affects Versions: 1.5.2
>            Reporter: Emmanuel Lecharny
>            Assignee: Stefan Seelmann
>             Fix For: 1.5.3
>
>
> When you want to see Operational Attributes, you may have to modify two parameters :
> - one on the connection (then the connection will be closed and reopened)
> - one in the entry's menu
> It would be convenient to add such a capacity in an entry contextual meny (ie, right
click on the entry on the browser) to expose those values. of course, if you switch to another
entry, then you won't see the opattrs unless you do the same action.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message