Hi — I’m an independent developer testing a small, self-service Forge beta for Jira Service Management Assets admins who import CSV files.
The problem I’m testing: CSV issues are often found too late, after an import has already failed or produced an unexpected result.
Assets Import Preflight runs before the real import:
- parses and validates the CSV in the app page
- reports exact row and column errors
- checks required values, duplicates, and common Assets data types
- optionally compares the selected identifier with existing Assets objects to estimate Create vs Update
- cannot create, update, or delete Assets objects
Privacy and architecture
- no CSV, filename, row, identifier, or error-report storage
- no third-party analytics and no external network egress
- only counter-level Forge metrics; no CSV content or email addresses
- the optional preview sends selected identifier values only to the customer’s own Atlassian Assets API
Self-service beta flow
- Install the app.
- Open Assets Import Preflight in Jira.
- Load the demo or choose a CSV.
- Select the Assets schema, object type, and identifier.
- Validate and run the read-only preview.
Free beta: Assets Import Preflight
I’m specifically looking for people who already use JSM Assets CSV imports. The useful signal is whether you can reach a real-data preview without a call, custom setup, or help from me. If the workflow is not self-explanatory, that is a product failure signal—not an invitation for manual onboarding.
If you try it, a useful reply would be:
- Did you reach a real preview without help?
- What stopped you, if anything?
- Did the reported row/column error match the problem in your CSV?
Please do not post or send CSV contents or identifiers. Community replies are enough; no email or meeting is required.