The requested improvements are:

1. Automatic field mapping during CSV import
   If a CSV column header exactly matches a Jira field name, the importer should automatically:

• Select the corresponding Jira field in the mapping dropdown, and
• Enable the “Map field value” option by default.

      2. Improvements to Time Tracking fields

• In our Jira instance, time tracking is displayed to users in hours and minutes. However, when importing issues from CSV, the values must be provided in seconds; otherwise, Jira rejects the import.
• This makes the process inconvenient for end users, because they must manually convert hours into seconds before importing the file. Ideally, the importer could accept common time formats (for example 2d, 1h 30m, or 90m) and convert them automatically.

       3. Improved handling of date formats
           The date fields currently require a specific format such as 6/Mar/26. This is not very intuitive for users preparing CSV files. It               would be very helpful if the importer could either:

• automatically detect the system’s default Jira date format and accept it during import
• or be more flexible and interpret common date formats (for example 2026-03-06, 06/03/2026, etc.) and convert them internally