Your feedback drives the Concourse roadmap! Review and vote for existing ideas or submit new ideas.
For immediate technical support, please follow this guidance to open a Service Now ticket.
Put Simply:
Improve Jira’s CSV upload functionality so that the “Original Estimate” field accepts not only seconds (XXs), but also additional time units such as weeks (XXw), days (XXd), hours (XXh), and minutes (XXm).
What is the problem?:
In the current Jira CSV import process, the Original Estimate field only accepts values in seconds, unlike the Jira UI, which supports multiple time units (w/d/h/m).
As a result, teams that manage effort estimates in Excel or external systems must manually convert all values to seconds prior to upload, increasing operational overhead and causing potential human error.
There is an inconsistency between the UI input experience and the CSV import requirements, leading to confusion and poor user experience.
Integration with external tools becomes cumbersome due to the need for format conversions, creating friction in workflows and reducing efficiency.
What needs to be developed?:
Extend CSV import logic to allow the Original Estimate field to accept the following formats in addition to seconds (XXs):
XXw (weeks)
XXd (days)
XXh (hours)
XXm (minutes)
Implement internal logic that correctly translates each of these formats into seconds, consistent with Jira’s time‑tracking model.
Add robust validation and error messaging for invalid formats (e.g., free-text inputs, unsupported mixed-unit expressions like “1w2d”, or non‑numeric values).
Ensure performance and reliability when processing large CSV files.
Align CSV input behavior with Jira UI expectations to create a consistent and intuitive user experience.
Kazuki Nagai
| Workspace Territory | Japan |
Thank you for taking the time to share this idea and clearly explain the impact to your team. At this time, the CSV import behavior for the Original Estimate field is native Jira functionality managed by Atlassian, and we’re unable to modify or extend that logic within our environment. Since this would require a product-level change, we’re unable to move forward with the enhancement, but we appreciate you raising the opportunity for improvement.