Can Jira import a column from an xlsx file into a checkbox or action-item field, and if so, how do I

Hello @Eric Pujo , @Gor Greyan has it right, and it is worth spelling out exactly why, because the boundary here is precise.

Why the import cannot create checkboxes in the description: the interactive checkboxes you see in Jira descriptions are the native action items feature, created in the editor by typing [] followed by your text. Action items have no wiki markup or markdown token at all, which has been confirmed repeatedly by the community and Atlassian's own text formatting notation, there is simply no code that means "checkbox". The CSV importer writes text and markup into Description, so with no markup token to write, no import (and no automation rule) can produce them today.

What the import CAN do to the description: wiki markup in your Description column survives the import, so you can turn your Excel column into a formatted list. Build the Description cell in Excel by joining the values with a line break and a leading asterisk (* item one, * item two), and during import leave "Map field value" unchecked for the Description field, otherwise the importer strips the formatting. Official reference: https://support.atlassian.com/jira/kb/during-csv-import-the-formatting-of-description-field-contents-gets-removed/. You get a clean bulleted checklist to read, just not clickable.

Your three real options, by how much you need the tick behaviour:

1. Just need the values visible in the description: the wiki markup bulleted list above. Simplest, fully import-driven.
2. Need actual tickable data: Gor's recommendation is the right one, a Checkbox custom field mapped during import. The ticks then live in a structured field you can search and report on, which the description can never give you.
3. Need true action items in the description at scale: the only programmatic route is the REST API, writing the description as an Atlassian Document Format taskList after import (reference: https://developer.atlassian.com/cloud/jira/platform/apis/document/structure/). That is real scripting effort, so I would only go there if the interactive-checkbox-in-description behaviour is a hard requirement.

For most cases like yours, option 1 for readability plus option 2 for the data is the combination that works, and both happen in one import.

Hi @Eric Pujo

Welcome to the Atlassian Community

If you want the Excel column to become an actual Jira Checkbox custom field, Jira Cloud's CSV importer supports mapping CSV data to an existing Checkbox field.

https://support.atlassian.com/jira-software-cloud/docs/mapping-csv-data-to-jira-fields

If you mean interactive action-item checkboxes inside the Description, the CSV importer does not provide a direct Excel-column action-item conversion. Mapping a column to Description imports its content as text/rich-text content; it doesn't automatically transform each value into Jira action items.

So if the requirement is simply selectable options, I would recommend creating a Checkbox custom field and mapping the Excel/CSV column to it during import.

Regards,
Gor

@Eric Pujo 

Based on my experiences, this dead-simple flow could work:

1. You copy-paste the the Excel values to the Description field.
2. Click the "Rovo" icon in the bottom-right, and ask the AI using a prompt similar to this: "Make each line a separate checkbox item."

I used Rovo to make these kind of "codified mass updates" with great success.