How to sync Epic Name field?

General Questions
, , , ,
1

Originally asked by Anette Huber-Kemmesies on 03 February 2022 (original question)

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

Comments:

Thomas Weichel commented on 10 February 2022

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?

Thomas Weichel commented on 15 February 2022

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

Have you a Tip what can i do here?

2

Answer by Francis Martens (Exalate) on 20 February 2022

Hi Thomas Weichel

Did you check on following document
https://docs.idalko.com/exalate/display/ED/Cannot+sync+the+Epic+name+field

Francis

Comments:

Thomas Weichel commented on 21 February 2022

Hello Francis Martens (Exalate)

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

Francis Martens (Exalate) commented on 21 February 2022

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.

Thomas Weichel commented on 22 February 2022

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

Francis Martens (Exalate) commented on 22 February 2022

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.