Issue exporting failure

[スズキ]

Hi.

I'm trying exporting issues by "BETTER EXCEL EXPORTER".

Then first row exporting fails like below:

1. Column Using "fieldHelper.getFieldValue"(Custom value)
Can't get the value ONLY at first row.
(Can get it at second row and below)

2. Column Using "issue.xxx"(System value)
Can get the value normally at all rows.

How can I get Costom Value from first the row?

(Sorry for my poor English because I'm Japanese...)

[Natalia_Kovalchuk_SaaSJet_]

Hi スズキ!

In case you would be open to considering other apps for export, you might take a look at Issue History for Jira (Work Item History) from SaaSJet as an alternative solution.

It allows you to generate structured Excel reports that include the full work item history (including custom field changes, status transitions, comments, and field updates) in a clear, tabular format.

[Aron Gombas _Midori_]

@スズキ I'm working on this app.

Can you please show a screenshot that illustrates the problem? I can't totally understand the error as described in your original post.

[Prasanna Ravichandran]

Hi,

This usually happens due to how Better Excel Exporter initializes custom field values for the first row.

Try the following practical checks:

1) Use the field ID instead of field name**

Sometimes the helper fails to resolve the custom field by name on the first row.

Example:

fieldHelper.getFieldValue("customfield_12345")

2) Check if the first issue actually has a value**

If the first issue has an empty/null value, the exporter may return blank only for that row.

3) Use a null-safe expression**

$fieldHelper.getFieldValue("customfield_12345") ?: 

4) Ensure the field is available on the issue’s screen/context**

If the custom field is not applicable to that issue type/project, it may not load for the first row.

 If the issue still occurs, it may be a template evaluation limitation. In that case, try updating to the latest version of Better Excel Exporter or contact the vendor support with a sample template.