How to export Jira issues to Excel with assignee email addresses and due dates

A program manager looks after scope, timeline and budget. For the timeline, the Gantt chart gets built bottom-up, through a series of long working sessions such as intensive planning sessions (IPS). After that comes the part that never ends: following up on the individual tasks with different people to make sure they’re actually moving as planned. That means meetings with task owners, stand-ups and emails, and a lot of manual check-ins that take real time. All of it starts with one list: every task, its owner, the owner’s email and the due date. In Jira, the email is the part that’s missing.

Why the Jira CSV export has no email column

Since Atlassian’s 2019 privacy changes, Jira Cloud identifies people by an account ID instead of a username, and the CSV export follows suit. For a user field like Assignee or Reporter you get two columns: the display name, and a second column with the account ID. Nothing in the export field list gives you the address. Atlassian’s own knowledge base says the field list has no field that shows the reporter’s email, and a public suggestion to put emails in the CSV export has been open since May 2019.

So if you want to email owners about their tasks, or load the list into another tool, you need a second source for the addresses.

Step 1: export the issues with the right columns

1. Go to Filters → View all work items (Jira now calls issues “work items”) and write the JQL for the work you report on, for example project = ABC AND statusCategory != Done ORDER BY duedate.
2. Switch to the list view and add the columns you need: Summary, Assignee, Due date, and Start date if your project uses one.
3. Open the ••• menu, choose Export, then Export Excel CSV (current fields). The account ID columns for user fields are included even with “current fields”.

Jira Cloud exports up to 10,000 work items at a time, in the background; you get a notification with the download link. Atlassian recommends opening your data with the Open in Microsoft Excel or Open in Google Sheets buttons instead of uploading a downloaded CSV into a spreadsheet, because a CSV can carry formulas that run when it opens.

Step 2, option A: Jira Cloud for Sheets

Jira Cloud for Sheets is Atlassian’s add-on for Google Sheets. In the side panel choose your site, then Get issues from Jira, enter your JQL, and under Fields add Assignee.emailAddress next to Summary, Assignee and Due date. Then Get issues now, and download the sheet as .xlsx if you need it in Excel.

This is the quickest route when it works. When it doesn’t, the cell shows [no subfield found]. That happens when:

• The person hides their email. In their Atlassian profile, under Profile and visibility → Contact → Email address, “Who can see this?” is set to “Only you and admins”. Only they can change it.
• The site hides all emails. A Jira admin sets User email visibility under Settings → System → General configuration to Public, Logged in users only, or Hidden. The site setting wins over the person’s own.

So expect gaps on a site where emails are locked down, and don’t send anything from the list until every row has an address.

Step 2, option B: the admin user export, joined on account ID

An organization admin can export users with their email addresses from Atlassian Administration: Directory → Users → Export users (on the older admin layout, open the site, then Users). They can limit it to active users and to the groups your project uses. Atlassian emails them a download link. The CSV starts with User id, User name and Email.

Put both files in one workbook: the issue export on a sheet called Issues, the user export on a sheet called Users. Then add an Email column to Issues that looks up each assignee’s account ID.

=XLOOKUP(C2, Users!A:A, Users!C:C, "no match")

Older Excel without XLOOKUP:
=IFERROR(INDEX(Users!C:C, MATCH(C2, Users!A:A, 0)), "no match")

Match on the ID, not the display name. Two people can share a name, and names change; the account ID doesn’t. Filter the new column for “no match” before you use the list: those are usually unassigned issues or people who have left the organization.

This route needs an admin, and a user list with every email in the organization is personal data. Ask only for the groups you need, keep the file out of shared drives, and delete it when you’re done.

Step 2, option C: ask for the list once

On a small project the fastest path can be a message to the team: “Reply with the email you want task reminders sent to.” It’s slower than a lookup but needs no admin and no add-on, and it tells you which address each person actually reads.

Which route to use

In practice, a combination: an automated way to build the list and send the requests, plus a short in-person conversation first. Tell people you’ll be collecting their emails and that task update requests will come by email. Sharing that up front means nobody is surprised by the first one, and nobody mistakes it for spam.

Getting the due dates into Excel as dates

Jira writes dates in the export using your site’s date format, so Excel may read them as text. Check by selecting the Due date column: if the cells are left-aligned or a sum shows zero, they’re text. Select the column, then Data → Text to Columns → Next → Next, choose Date with the order your dates use (for example DMY), and click Finish. Blank due dates stay blank, and those are worth a question of their own: a task with no date can’t slip, so it never shows up as late.

Checklist before you send anything from the list

• Every open task has an assignee, and every assignee has an email (no “no match”, no [no subfield found]).
• Due dates are real dates, and blank ones have been asked about.
• Rows are leaf work, not epics or parent issues whose dates roll up from children.
• The user export is deleted or stored somewhere only you can open.
• The team has heard from you, in person, that update requests will come by email.

What the list costs you after it’s built

On a big project with 30 or more people, sending 30 status emails can take a few hours, because each one needs some context: what the task is, why it matters now, and the best way to get a useful answer out of that person. Getting the addresses right is only the start.

Then come the problems a clean spreadsheet can’t fix. The hardest is response. People are busy and the email gets buried in their inbox. The wrong person gets it. The owner decides the task is no longer relevant and simply ignores it. Meetings don’t solve it either: a check-in or stand-up overlaps with something else and gets deprioritized. So collecting dates is hardest exactly when they’re urgent, and the gap gets filled with manual follow-up.

Skipping the export

If the reason you want this list is to ask owners for status, PingCadence can read the project instead. Click Connect Jira, approve access to your Atlassian site and pick a project; it reads issues, assignees and due dates (plus a Start date field if you have one), emails each assignee a short check-in from your own Outlook or Gmail, and sends approved due-date changes back to Jira. See the Jira integration.

If you have to rebuild this list every week, have patience, and don’t try to do everything. Follow the Pareto principle: identify the few tasks on the critical path and put most of your follow-up there. Chasing every task every week becomes too much work, and the few critical ones drive most of the result.

For the same problem in Microsoft Project, where the resource emails live in the Resource Sheet, see how to export Microsoft Project with resource email addresses.

Jira menus are from Jira Cloud as of November 2026. Atlassian documents the export in Export search results and Export over 10,000 work items in Jira Cloud, the missing email field in How to export the reporter’s email and JRACLOUD-72001, the visibility settings in Resolving email visibility issues and “No subfield found” in Jira Cloud for Sheets, and the user export in Export users from a site.