If you're trying to import issues and sub-tasks in the CSV, then the issue-id either ends up as being the actual issue key for existing issues or pulled into the external-id field if it's for a new issue.
The sub-task's parent-id is not imported - it gets converted to the issue key of the parent issue.
Please provide sample data from your CSV file and show us how you have mapped the fields during the import.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
is it a good practice to include issue id and parent id in csv file?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, if you need to update existing issues, add sub-tasks to them, or your import contains a mix of issues and their sub-tasks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Then the data will be imported as new issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.