Uploaded image for project: 'Go2Group CRM Plugin'
  1. Go2Group CRM Plugin
  2. PLUGINCRM-773

When matching JIRA users to email addresses, case should not matter

    XMLWordPrintableXML with Synapse FieldsWord with Synapse FieldsPDF with Synapse FieldsPrintable with Synapse...Word with Synapse FieldsPDF with Synapse FieldsWord with Synapse FieldsPDF with Synapse FieldsPrintable with Synapse...

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Significant
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.1.2
    • Security Level: Public
    • Labels:
      None

      Description

      I found a quirk in the CRM plugin that is going to severely impact our usage.
      When creating a JIRA issue from SFDC using a "Create Issue" button it passes the "Owner Email" to JIRA to populate the "reporter" field.
      Unfortunately SFDC forces all email addresses to lower case and the Active Directory our JIRA instance is referencing has mixed case email addresses. The CRM plugin compares the two using a case sensitive comparison and this results in the following error message:

      A JIRA user must be specified as the reporter when creating new issues.

      Check your JIRA/CRM Field Mapping settings for 'reporter' or specify 'reporter' or 'jira_user' in the URL.
      The value for 'reporter' may be a JIRA user name or a unique JIRA user email address

      This blocks issue creation even though there is a match when using a non-case sensitive compare:
      jonathan.sword@genband.com (SalesForce.com)
      Jonathan.Sword@genband.com (JIRA / Active Directory)

        Attachments

          Activity

            hide-sla-details-panel

              People

              Assignee:
              wwestmoreland Wayne Westmoreland
              Reporter:
              jsword Jon Sword
              Participants:
              Request participants:
              None
              Organizations:
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Salesforce