We are running JIRA 6.3. I am importing the issues from our old issue tracker cvstrac via a csv file, somehow during field mapping, issue status does not show up from the JIRA side to be mapped to. Thus all the imported issues end up in the "New" status. Did I miss anything here?
Could you please let me know what is the proper way to map issue status? Any help is very much appreciated.
Ahh, Chris, I think you're using the 'Import Issues from CSV' feature rather than the 'External System Import'. You want to go to Admin -> System -> External System Import -> Import from CSV and use that tool. The tool I think you're using is available to anyone who can do bulk updates (available from the Issues dropdown) and has limited capabilities. The admin tool will be able to update all fields.
Thanks for the explanation, Mikey. Indeed, I did confirm that I am able to map Status and Resolution when I use the External System Import as an administrator but I can't map those fields when I use Issues ->Import Issues from CSV. This is disappointing as I wanted a way to allow my testers to import test results on their own.
Can only be mapped to existing workflow statuses in JIRA. If not specified in your CSV file, imported issues will be given the default (i.e. first) Status as specified in your JIRA system.
Hmm. Curious. I can affirm that I've definitely mapped statuses using the CSV importer before. Are you mapping to a new project or into an existing project? I'm wondering if you need to map into an existing project for it to have a workflow to reference for statuses.
Same issue here with Jira Cloud. Status and Issue Type field not available in list of Jira fields to map into. Mikey Schott above seemed to indicate this required using External System Import, but also indicated Status field should be available in the normal bulk import tool. this is also indicated in Atlassian support docs, which reference importing to Status field via the bulk import tool. Please advise. thanks!
Hi, @Bryan Pace. I'm not sure if status can be mapped using the standard user-facing bulk CSV import tool, and the current documentation on this for Cloud doesn't mention mapping of statuses: https://confluence.atlassian.com/jiracorecloud/creating-issues-using-the-csv-importer-765593817.html . This is likely to prevent users from overstepping permissions and workflow restrictions in the target project.
What is your goal for the import? Do you have access to the admin CSV importer?
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG