Uploaded image for project: 'Crowd Data Center'
  1. Crowd Data Center
  2. CWD-1708

Rename "Use Relaxed DN Standardisation" option to avoid confusion

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 2.1
    • None
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Rename "Use Relaxed DN Standardisation" option from the LDAP Connectors to avoid confusion.

      This name does not reflect what the option is about (the understanding is not immediate).

      Suggestions:
      "Relax LDAP parsing"
      "Relax parsing"
      "Best Effort parsing"
      "Relax DN parsing"

            [CWD-1708] Rename "Use Relaxed DN Standardisation" option to avoid confusion

            Daniel Kinzler added a comment -

            great, thanks!

            Daniel Kinzler added a comment - great, thanks!

            SarahA added a comment -

            I'm not feeling all that homicidal today.

            (Crowd's ever-watchful faithful tech writer.)

            SarahA added a comment - I'm not feeling all that homicidal today. (Crowd's ever-watchful faithful tech writer.)

            David O'Flynn [Atlassian] added a comment -

            Hi Daniel,

            I like "Naive DN Matching". We'll change it in 2.1 - I wouldn't want to rename a checkbox in a point release; it'll just confuse people (and make our tech writers want to kill me ).

            Cheers,
            Dave.
            Crowd Product Manager

            David O'Flynn [Atlassian] added a comment - Hi Daniel, I like "Naive DN Matching". We'll change it in 2.1 - I wouldn't want to rename a checkbox in a point release; it'll just confuse people (and make our tech writers want to kill me ). Cheers, Dave. Crowd Product Manager

            Daniel Kinzler added a comment -

            I support the naming of this function, which I suggested in CWDSUP-2170. However, the alternatives suggested above would not improve the situation much: "relaxed" implies that by enabling it, comparison would be more lenient – the opposite is the case. "parsing" implies that the DN's syntactical structure is actually considered - this is not the case when this feature is enabled. "best effort" would imply that that all options are exploited before giving up - which is not true when this option is enabled.

            So, I propose to use the adjective "fast", "simple" or "naive" and the noun "comparison" or "matching", giving e.g. "fast DN comparison",
            "naive DN matching", etc.

            Daniel Kinzler added a comment - I support the naming of this function, which I suggested in CWDSUP-2170. However, the alternatives suggested above would not improve the situation much: "relaxed" implies that by enabling it, comparison would be more lenient – the opposite is the case. "parsing" implies that the DN's syntactical structure is actually considered - this is not the case when this feature is enabled. "best effort" would imply that that all options are exploited before giving up - which is not true when this option is enabled. So, I propose to use the adjective "fast", "simple" or "naive" and the noun "comparison" or "matching", giving e.g. "fast DN comparison", "naive DN matching", etc.

              pkuo Peggy
              rbattaglin Renan Battaglin
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: