While importing Due Date and Original Estimate into Jira using a CSV file

[mummareddy supriya]

While importing Due Date, Original Estimate, and Remaining Estimate into Jira using a CSV file, the following issues were observed:

1. Due Date and Estimates not updated after import

   • For Due Date, formats such as yyyy/MM/dd and MM/dd/yyyy were used.

   • Due Date

     2026/Mar/26

     2026/Mar/26

     Original Estimate

     18000

     3600

     18000

   • For Original Estimate and Remaining Estimate, values were provided in seconds.
   • During CSV validation, no errors or warnings were reported.
   • However, after the import was completed, the created issues were not populated with the Due Date, Original Estimate, or Remaining Estimate values.

2. Issue link direction not applied as expected

   • The project has a custom issue link type Verification, configured as:
     • Inward link: verifies
     • Outward link: is verified by

     • Outward issue link (Verification)

       R14.01.01_SWE5

   • During the CSV import, mapping was attempted using both:
     • Inward issue link (Verification)
     • Outward issue link (Verification) (tested separately in different imports)
   • Despite this, after import, the linked issues consistently appear only as “is verified by”, and it is not possible to obtain the “verifies” relationship through CSV mapping.

Observation

Both behaviors occur without any validation errors, which makes them difficult to detect during the import process.

Request

Has anyone figured out a reliable way to populate Due Date and Estimate fields during Jira CSV imports, and also set up “verifies” links via the same import? Would love to learn from any existing solutions or experiences.

please share your guidance.

Thank you in advance for your support.

[mummareddy supriya]

@Marc -Devoteam-

I tried exporting the same fields from similar issues that need to be imported and used the same formats for Due Date and Original Estimate. However, after importing, the time‑tracking fields still did not update.

[Marc -Devoteam-]

Hi @mummareddy supriya 

Best practice here is to export an or some issues in the space where you want to import issues.

Open the export in a plain text editor to see how the date and estimations are formatted.

Make sure the the CSV for import uses the same formatting.

For linking, you can only specify "outward" link options not inward. You need to use the same logic as for importing sub-tasks.

See, https://support.atlassian.com/jira/kb/how-to-import-issue-links-from-a-csv-file-in-jira/ 

[Marc -Devoteam-]

HI @mummareddy supriya 

See https://confluence.atlassian.com/jirakb/importing-original-estimate-time-spent-worklogs-and-remaining-time-using-csv-in-jira-1540724408.html 

[mummareddy supriya]

If the Create screen does not include Due Date, Original Estimate, and Remaining Estimate, is it still possible to update these fields through a CSV import?

[M Chandra Shekar]

Hi @mummareddy supriya Please avoid using plain numbers for the Original Estimate field. Instead, use Jira-supported time formats such as 1w, 1d, 1h 30m, 2h, or 45m.

Also, ensure the Due Date is provided in the correct format: dd/MMM/yy (for example, 25/Mar/26).

For issue linking, make sure to use the outward link type while defining the relationship in the CSV.

This helps ensure the CSV import works correctly without errors.