Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
/
Zendesk integration
Updated Jan 11, 2021

    Zendesk integration

    • 1 Zendesk-Jira Integration
    • 2 Known issues
      • 2.1 Missing ‘jira_escalated’ label
      • 2.2 Missing Data at ‘Issue Created’ event

    Zendesk-Jira Integration

    Zendesk is a platform that assists in providing support to customers. Zendesk can be integrated with Jira usign two apps, one on Zendesk and the second in Jira. These apps are listed below, along with a setup guide.

    • https://www.zendesk.com/apps/support/jira/

    • https://marketplace.atlassian.com/apps/1211941/zendesk-support-for-jira?hosting=cloud&tab=overview

    • https://support.zendesk.com/hc/en-us/articles/203660206-Using-the-Zendesk-Support-for-Jira-integration

    Known issues

    Missing ‘jira_escalated’ label

    Using the Zendesk-Jira integration tool it is possibel to create a Jira ticket through Zendesk. When a Ticket is created through Zendesk the issue is given a label automatically called ‘jira_escalated’. This label is hard coded and will always be generated by tickets created by Zendesk.

    Issue creation in Zendesk

    Issue in Jira

    Issue creation in Zendesk

    Issue in Jira

     

     


    However, the ‘jira_escalated’ label is added to the issue after the ‘Issue created’ event. As such the issue does not have the label when it is processed by JEMH. This can result in some processes such as user made scripts failing as they may depend on the ‘jira_escalated’ label.

    This issue only applies to the ‘jira_escalated’ label when it is auto created, if a user manually adds the label to the issue in Zendesk, the label will be present.

    The solution to this issue is to remove dependency to the ‘jira_escelated’ label from scripts and use other fields to identify issues created by Zendesk. Information on how this can be done can be found in this article, under ‘Custom Fields’:

    • Customize Email Templates | Custom FieldsPreview

    Missing Data at ‘Issue Created’ event

    When using the Zendesk - Jira integration tool alongside feature such as JEMH Templates, Information relating to the issue may not be present and thus cannot be used. This table illustrates when data added by users is available for use at the Issue creation event.

    Data set at Zendesk - Jira Issue create

    Data available at Issue creation event.

    Data set at Zendesk - Jira Issue create

    Data available at Issue creation event.

    Data Field left ‘Blank’

    Default Jira Value used during event, set to ‘Blank’ after event.

    Data field set to valid value on issue creation screen.

    Value available during issue creation event.

    The Plugin People
    Teams
    , (opens new window)

    Knowledge Base
    • How-to articles
      How-to articles
       This trigger is hidden
    Results will update as you type.
    • Event Listener JSD issue transition notifications do not send if a comment is present in the transition
    • Exception during issue update validation for non-Service Desk issue
    • File Attachments cause Out Of Memory problems
    • Gmail confidential mode
    • How to supply a default value for the Tempo Account custom field
    • How to support email addresses with international characters
    • Issue fails to create with indexing errors
    • JEMH Is not yet licensed through Atlassian Marketplace
    • JIRA fires Issue Assigned event for newly created Issues
    • Jira Service Desk problems
    • Jira 7 *Wrong JVM Version!* Error
    • JSD Organization field
    • Mail fails to be retrieved from mail server
    • MYSQL exception - Caused by: java.sql.SQLException: Incorrect string value
    • MYSQL Duplicate entry '0'. No Valid License
    • Non-JIRA recipient custom field values have been updated but JEMH is notifying the old values
    • Notification History tab does not show on issues
    • Problems with IMAP
    • Problems with POP
    • Slow Jira startup with PostgreSQL
    • Sorry, you can't create any issues right now, as you need to have access to a JIRA application to be able to create issues
    • You do not have permission to assign issues
    • How to change the event type of a notified event
    • Diagnose no inbound mail handled
    • JSD (Jira Service Desk) - Who is notified when?
    • HTML extraction method to Wiki mark up
    • Setting System Fields using Script Field Processor
    • Test case editor fails to load
    • MessageRemovedException in log files during email processing
    • Characters appearing as question marks
    • UI not visible after upgrading to version 3+
    • Default Project Mapping and unwanted inheritance causing inbound mail to be forwarded
    • JEMH is disabled on startup in Manage Apps
    • Configure JSD Customers for use with JEMH
    • Custom Field values are cached causing recipients to not receive notifications (JIRA 7.3.0 - 7.3.4 , JEMH 2.1.0 - 2.1.11)
    • Restrict commenting to one project
    • Foreign key constraint violation during Audit Event history purge
    • Request participants not sent JEMH notification
    • Handling out of disk space
    • Profile import timeout error
    • Zendesk integration
    • Outlook sending formatting
    • Attachment links added as comments, Jira Service Management/Desk
    • Incoming Auditing Actions Error Popup
    • Updating JEMH's issue event listener to listen for IssueEventBundle's (JEMH-6994)
    • Template Set Responsibility Devolution (JEMH-5403)
    • Support non-ascii characters in email addresses (JEMH-6431)
    • Custom Fields don't get added during creation phase causing creation notifications to not fire for User/Group field types. (JEMH-306)
    • Cant stop reporter being added as a watcher (JEMH-790)
    • Handle re-index failure during watcher setup (JEMH-7180)
    • Inline User Macros sometimes don't render (velocity 2.0 needed) (JEMH-5536)
    • "Stuck" emails in queues after post condition test (JEMH-5366)
    • Dealing with 'Undisclosed Recipients' (JEMH Server/DC)
    • Missing Methods in TemplateIssue Class since Jira 8.19.0
    • Why do FolderClosedException occur
    • Customer Permissions for Request Participants
    • User Anonymization Fails - SQL Server 2019
    • Maintaining JEMH Attachment Property Set values
    • Display Issue Notifications in Right To Left Languages
    • Jira Server/DC - when mail polling stops, fixing without a Jira restart
    • A3 BAD User is authenticated but not connected error message when using JIRA with Office365
    • JEMH not enabling on upgrade to Jira 8.13.x and 8.20.x LTS releases made after 23-MAY-2022
    • Using an inactive user with user creation enabled
    • Missing Created/Timestamp Columns Causing Problems
    • -1 Values for the "Comment count limit" and "Comment char length limit" in the Default Project-Mapping
      Calendars
    You‘re viewing this with anonymous access, so some content might be blocked.
    {"serverDuration": 12, "requestCorrelationId": "c13238a6a53b4a5ab86f62d7436c9f47"}