Page Comparison

How it works:

1. Navigate to Administration → Manage apps → Smart Checklist Settings.

2. Click on the "Import Checklists" tab.

3. Select an app to import from the list:

   1. My ToDo;

   2. Elements Checklist.

4. Click on the first tab link that redirects you to the "Projects" tab.

5. Toggle Smart Checklist on for the projects for which the import needs to be done.

6. Come back to the "Import Checklists" tab.

7. Select an app to import from the list one more time (My ToDo/Elements Checklist)

8. Choose one option to import:

   1. Override existing Smart Checklist items - will replace checklist items that you already have in Smart Checklist with the ones from another app.

   2. Append to existing Smart Checklist items - will add checklist items from another app to the bottom of the checklist that you already have.

   3. Add to issues with empty Smart Checklists data only - will run import only for the issues where Smart Checklist is empty. Checklists from the other app will be added.

9. Click "Run import". The import will start.

10. You will see the progress bar for the import. The importing process will take some time.

11. Once it is completed, the date and time of the last import will be displayed. A message with the number of successfully/not migrated checklists will be shown. Additionally, you'll see a link to the detailed log that could be downloaded.

...

If the source plugin is not installed on the instance you will see this option as grey with a “not installed” tag and it will not be possible to select it from the list.

...

Migration using API

There is also an option to run the import from another app on a project basis. It can be inconvenient for users to ask the admin to enable/disable all other projects on the settings page, so there is a possibility to run project migration by project admin when it is needed. It can be done using the REST API endpoint.

...

POST /rest/railsware/1.0/migration

Body parameters (application/json) - list of JSON objects:

• migrationOption: string

• migrationType: string

• projectIds: number (optional)

Example

Run migration from Elements Checklist app to Smart Checklist with override option for 2 projects:

{
    "migrationOption": "OVERRIDE",
    "migrationType": "ELEMENTS",
    "projectIds": [11001, 10900]
}

Formatting

You can find the direct formatting conversions that will be applied to checklists during import in this table:

Formatting types	Description	Displayed in Smart Checklist
Import from My ToDo
Statuses Status colour Blue title TO DO	It's highly recommended to manually create the same custom statuses you had in My ToDo in Smart Checklist before the import. If, during import, some statuses are missing, they will be created with a similar name but with “Unchecked” state as default in Smart Checklist
Links 🔗	Links are supported and migrated in this format: Code Block - [marketplace](https://marketplace.atlassian.com/apps/1211170/my-todo?hosting=datacenter&tab=versions) - link to Atlassian marketplace - [https://community.atlassian.com/t5/Jira-Service-Management/Setting-default-value-for-priority-field/qaq-p/770467](https://community.atlassian.com/t5/Jira-Service-Management/Setting-default-value-for-priority-field/qaq-p/770467)
User mention 👤	All users present in the User management under the instance and are mentioned in the checklists will be migrated successfully. Full name will be displayed
Date 📆	Dates are supported and will be rendered accordingly
Numbered/bullet point hierarchical lists 📜	As we are not supporting hierarchical lists it will be migrated as one item and rendered as number/bullet point lists
Text Formatting 🔤	Italic and code text is supported
Mandatory items (flagged items) ‼️	All mandatory items (that are flagged) are imported as typical ones as we don’t support mandatory items as of now
Import from Elements Checklist
Multiple panels (checklists) 🔢	Unlike our product, Elements Checklist allows users to have more than one panel (checklist). When importing, the different panel names will be formatted into <h3> headers. The names of the attributes will be formatted into the <h6> headers in a row separated by |.
Separators 📏	"Separators" in the Elements Checklist are similar to our headers functionality. They start with: --- *** ___
Blockquotes	Blockquotes are not supported. They will be rendered as one item
Lists (Ordered/Unordered) 📝	Lists are not supported. They will be rendered as one item
Tables 📊	Tables are not supported. They will be rendered as one item
Links 🔗	Links are supported and will be rendered accordingly
Images	Images are supported and will be rendered accordingly
Text Formatting 🔤	Italic, bold, strikethrough and code text is supported
Headers	All 6 headers are supported and will be rendered accordingly
Formulas	Only basic formulas are supported All the number attributes together with result field will be rendered as a row separated by |
Files	Files are not supported. They will be rendered with id and file name

Attribute types

Elements Checklist in its panels can have a structure with different attribute types.

...