Questions for Confluence license has expired.

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

How to sync Epic Name field?

 
1
0
-1

Hi,

I connected following 2 instances: Jira A-Cloud, Jira B-Server). I get a "required field error" for following use case:

  • creating "Epic" in Jira B (all required fields are filled)
  • syncing
  • error Jira A: "Field Epic Name is required.: customfield_10011" → Epic Name is filled in Source Side (Jira B).

How can I sync the Epic Name field, so that no error occures?


Counter test:

  • creating an "Epic"- issue in Jira A (all required fields are filled)
  • syncing it to Jira B
  • → transmission successful, but required field "epic name" is empty


Thanks for your help!


Best regards

Anette



  1. Thomas Weichel

    Here some more Information to this topic.

    The synchronisation of the epics has to run from Jira Server to Jira Cloud.

    I have saved the script file epic.groovy under Jira Home scripts. ERpic Colour is set also on Jira Server and Jira Cloud.

    I add epic.send under outgoing rules but there comes an error if i start excalate.

    On Jira Cloud side comes the error Field Epic Name is required.: customfield_10011 without more Information.

    What have i to do that the epics can syncronised?


  2. Thomas Weichel

    Francis Martens (Exalate) or another one from the Team.


    Have you a Tip what can i do here?

CommentAdd your comment...

1 answer

  1.  
    1
    0
    -1
    1. Thomas Weichel

      Hello Francis Martens (Exalate) 


      yes i have checked this settings and they are active in the screen

    2. Francis Martens (Exalate)

      Please raise a ticket on our support portal

      https://support.idalko.com/servicedesk/customer/portal/8

      We need the permission to look into the exalate node to see what is going on.


    3. Thomas Weichel

      Hello,


      if it´s help der was already a support ticket open https://support.idalko.com/plugins/servlet/desk/portal/8/EASE-13090 and it was closed with the reason to open a Ticket in this community

    4. Francis Martens (Exalate)

      Oops - sorry.

      There is a thin line between support and configuration - and here it shows.
      We'll handle the case on support as it should work.

    CommentAdd your comment...