Microsoft Lists Import for Jira
Setup takes about 15 minutes. Here's how it works, step by step.
Before you start
You'll need:
- Jira Cloud (not Data Center or Server)
- Microsoft Lists or SharePoint lists, on a Microsoft 365 work or school plan that includes SharePoint
- A Microsoft 365 admin to approve the connection, once
- A Jira admin to install the app
Install the app
A Jira admin installs Microsoft Lists Import for Jira from the Atlassian Marketplace. In Jira, go to Apps, then Explore more apps, search for Microsoft Lists Import for Jira and select Get app.
Once it's installed, open it from Apps in Jira's top bar.
Set it up
Connect
Connect Microsoft 365 from inside Jira. A Microsoft 365 admin approves the connection once. Only Jira admins (and whoever they allow) can set it up.
Map
Pick a list and a Jira space. Shim suggests where each column goes in Jira, and which issue type each item becomes. Change whatever you want.
Preview
You get a list of every issue Shim is about to create or update, plus every value it can't copy over exactly and why.
Test
Run it on 5 items and go look at them in Jira. If something's off, undo the test and fix the mapping.
Go live
Shim moves the rest, and that's it. The list is in Jira.
What comes over
| In Microsoft Lists | In Jira |
|---|---|
| Items | Jira issues, one per item, with the issue type you pick |
| Columns | The Jira fields you map |
| Comments | Comments, with the name of whoever wrote them |
| Attachments | Attachments on the issue |
| Person columns | Jira users, matched for you |
| Parent and child items | Lists don't have them, so every item ends up at the same level in Jira |
When something goes wrong
If one item has a problem, Shim skips it and keeps going with the rest. The problem shows up in the app with an error code, what went wrong, and how to fix it. Here's one you might see in the preview:
Move the print room
Priority "Urgent" has no match in WORK. Pick a Jira priority.
Fix it, and Shim picks the item up again on the next sync.
An error code's first digit tells you where the problem is. E1 is the connection, E2 is Jira, E3 is your field mapping, and E4 is a field rule in Microsoft Lists.
Undoing changes
The 5-item test is there so you can check the result before anything else moves. If something's off, open the test in the app and select Undo test. Shim removes the issues the test created, as long as nobody has changed them since. If someone has, Shim leaves that issue alone and labels it instead.
Shim never deletes anything in Microsoft Lists.
Common questions
What does it bring over that a CSV import doesn't?
Comments (with who wrote them), attachments, and who's assigned to what (matched to their Jira accounts). A CSV import often skips those, or takes hours of cleanup to get them in.
Who has to approve the connection?
A Microsoft 365 admin, one time. After that, any Jira admin (or anyone they give access to) can take it from there.
Does it work with SharePoint lists?
Yes. Microsoft Lists are SharePoint lists under the hood, so they work the same way.
Our list doesn't have parent and child items. Is that a problem?
No. Each item just becomes its own Jira issue, using whatever issue type you pick.
Can I undo it?
That's what the 5-item test is for. Look at those items in Jira, and if something's off, undo the test, fix the mapping and try again. Shim never deletes anything in Microsoft Lists, either.
Can this replace our Power Automate flow?
If the flow just copies items into Jira, yes. If you also want the Jira status to show up in the list, you'll want Microsoft Lists Sync for Jira instead.
Is it really free?
Yes. Import apps are free for any size team.
What if we decide to keep using Microsoft Lists after all?
Then install Microsoft Lists Sync for Jira. It picks up where the import left off, so you don't have to map anything again.
Does it work with Jira Data Center or Server?
No, just Jira Cloud.
Still stuck?
Email [email protected], and include the error code if you have one. You'll hear back within one business day.