Questions for Confluence license has expired.

Please purchase a new license to continue using Questions for Confluence.

Set Multi-Level Cascading Select in JIRA Based on Fields in Zendesk

 
1
0
-1

How do I set a Multi-level cascading select field on jira based on fields in zendesk (even if the zendesk field is broken out into multiple fields, ie one drop-down for each level)?

    CommentAdd your comment...

    3 answers

    1.  
      2
      1
      0

      Hi Spencer,


      After doing some testing with this plug-in myself I see that the way to send the information in your data filter should be the following (jira):


      replica.customKeys."Location" = issue.customFields."Location"?.value?.value


      what you are sending is a list of strings so in Zendesk you're going to need to map that into a text field, that

      s what I think would be the easiest option.


      Let me know how this goes!


      Thanks,


      André

      1. Spencer Johnson

        I am trying to figure out how jira sends the field from the local payload but there is an error and the local replica is empty currently

      2. Spencer Johnson

        It didn't give an error but it didn't work:

        Here is the outgoing on the Jira side: 

        replica.customKeys."Location" = issue.customFields."Location"?.value?.value


        Here is the incoming on the zendesk side:

        if(replica.customFields."Location"?.value){ // Works
        issue.customFields."Location".value = replica.customFields."Location".value
        }



        On the zendesk side, Location in the remote replica comes in as 

        "customKeys": {
      "Location": [
        "Broadband",
        "AAFES",
        "AFMTHM Mountain Home AFB"
      ]
    },

        No location is shown on the local replica from the zendesk side
      3. André Leroy-Beaulieu Castro

        Hi Spencer,


        The line on zendesk should be:


        issue.customFields."Location"?.value = replica.customKeys."Location".join(",")


        Thanks,


        André

      4. Spencer Johnson

        That worked! Do you know how i would go from the other direction?


        Ie setting the multilevel cascading select field in Jira from the zendesk side (even if its broken out in multiple fields in zendesk)?

      CommentAdd your comment...
    2.  
      1
      0
      -1

      How would I go about the other direction? ie zendesk to Jira


      Here is the set up on the zendesk outgoing:

      replica.customFields."Location Part 1" = issue.customFields."Location Part 1" 
replica.customFields."Location Part 2" = issue.customFields."Location Part 2" 
replica.customFields."Location Part 3" = issue.customFields."Location Part 3"




      On the jira incoming, I want to combine those into one and set "Location"
      This is what I have currently but it isnt working

      issue.customKeys."Location" = [replica.customFields."Location Part 1".value, replica.customFields."Location Part 2".value, replica.customFields."Location Part 3".value]



      1. Spencer Johnson

        André Leroy-Beaulieu Castro I wanted to follow up on this

      2. Spencer Johnson

        I created this community question for the other direction:Set Multi-Level Cascading Select in JIRA Based on Field in Zendesk 

      CommentAdd your comment...
    3.  
      1
      0
      -1

      Hi Spencer,


      What error are you currently seeing? Is it in Jira or Zendesk? If you access the Entity Sync Status window in your Exalate app for Jira and look for the issue where you are trying this out, you can't see the local replica?


      Thanks,


      André

      1. Spencer Johnson

        Here is the error. It is on the JIRA side.

        There is no "Entity Sync Status" in the exalate app in Jira or at least none that I could find.

      CommentAdd your comment...