Epic Link field is missing in RawData exports on Cloud

This article is for Cloud.

Question

When exporting reports to Excel the field “Epic Link” is missing. Why is this happening?

Answer

This field isn’t being shown by Tempo on purpose. That’s because our developers identified in some specific cases there’s an unexpected value being returned when Tempo tries to get the issueFields.

They make a call to /rest/api/2/field to get the issueFields and, the following answer is received:

  {
    "id": "customfield_10006",
    "key": "customfield_10006",
    "name": "Epos-Name",
    "untranslatedName": "Epos-Name",
    "custom": true,
    "orderable": true,
    "navigable": true,
    "searchable": true,
    "clauseNames": [
      "cf[10006]",
      "Epos-Name"
    ],
    "schema": {
      "type": "string",
      "custom": "com.pyxis.greenhopper.jira:gh-epic-label",
      "customId": 10006
    }
  },

The parameter “untranslatedName” is not translated. That is the root cause of the problem, probably caused by migration issues. To allow customers with this problem on their instance to export reports, our team has hidden the error that was thrown and hidden the Epic Link field.

To fix this problem is necessary to ask the customer to get in touch with Atlassian. They can fix this unexpected value from their side and then, the Epic Link is going to appear normal again.

https://tempo-io.atlassian.net/browse/TCS-33114