# Bug JIM-101 - Jira Migrator gives unhelpful error message if user email is blank

Project: Stream Jira to OpenProject data Migrator
Status: closed
URL: https://community.openproject.org/work_packages/JIM-101

## Open points

_No work packages_

## Details

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Module |  |
| Target versions | 17.5.0 |
| Observed in versions |  |
| Sprint | Sprint 2 (within the cycle of 17.6) |
| Backlog bucket |  |
| Bug found in version (deprecated) |  |
| Requires doc change | No |
| Accessibility | No |
| Pull preview |  |
| List |  |
| Labels |  |

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Planning

| Attribute | Value |
| --- | --- |
| Relevance |  |

## Costs

| Attribute | Value |
| --- | --- |
| Votes |  |
| Work |  |
| Labor costs |  |

## Description

### Steps to reproduce

1.  Have an LDAP managing Jira users with a user account without an email. Then Jira has an account without an email

2.  Migrate a project where this user is involved.

3.  Then during migration you get an error message: Email can't be blank.

### What is the buggy behavior?

  - The error message does not have enough context to fix it properly. It is very hard to identify Jira user account with out an email from this error message. You have to find it manually.

### What is the expected behavior?

1.  Error message contains enough details to identify Jira account without an email address.
