Issue Summary

When refreshing a Jira Cloud for Excel JQL import into an existing worksheet using Refresh Data / Replace current sheet, the add-in overwrites the rows returned by the new query but does not clear rows that were populated by the previous, larger result set.

For example, if the initial import returns 50 issues and a later refresh returns 40 issues, rows 41-50 retain data from the initial import. This can lead to inaccurate reports unless the user manually clears the worksheet before every refresh.

This matches the historical symptom reported in API-199, which was closed as Cannot Reproduce. A current customer recording is available internally in support ticket PCS-3838464.

Steps to Reproduce

1. In Jira Cloud for Excel, import a JQL query into an active worksheet that returns a known number of issues, for example 50.
2. Modify the JQL query or underlying issue data so the same import returns fewer issues, for example 40.
3. Use Refresh Data and select Replace current sheet.
4. Review the rows below the final row returned by the refreshed query.

Expected Results

The refresh replaces the previous imported data and clears data from rows that are no longer included in the refreshed result. In the example above, only the 40 current issues should remain in the worksheet.

Actual Results

The add-in updates the first 40 rows but leaves the values from the previous import in rows 41-50. The worksheet therefore contains stale Jira data that is not present in the current query result.

Workaround

Use the built-in =JIRA.JQL() dynamic array formula in a clean worksheet, as it resizes to the current result set on recalculation.

Other mitigations include importing to a new worksheet, manually clearing the previous output range before refresh, or using a VBA macro to clear the target worksheet before the add-in refresh.