Frequently Asked Questions (FAQ)
Below are some of the most common questions about configuring and using Admin Essentials.
Q: Why won't Jira let me save the issue and shows an error on the Email field?
A: The add-on validates email format on the server. The error appears when: 1) the text does not match a standard email format (for example, missing @ or containing spaces), 2) the address exceeds the 254 characters allowed in total, or 3) the part before @ exceeds 64 characters. Correct the address and save again.
Q: Does validation also apply when I create or update issues through the REST API?
A: Yes. Validation runs on the server as part of Jira's standard custom field lifecycle, so it applies uniformly from Jira screens, the REST API, importers, and external integrations. This prevents invalid addresses from entering through alternate paths.
Q: Can I search for issues by Email field value from JQL?
A: Yes. The field is registered with a searcher integrated with Jira's engine. You can use queries such as "Field Name" = "client@example.com", replacing Field Name with the exact name assigned when creating the custom field.
Q: I created the field, but users don't see it on the issue screen. What's missing?
A: In Jira, custom fields only appear on screens they have been explicitly associated with. Verify that the Email field is included in the project's screen scheme (for example, on the default, create, and edit issue screens).
Q: Can I store more than one email address in the same field?
A: No. The Email field stores a single address per issue. If you need to capture multiple addresses (for example, a notification list), we recommend creating separate Email fields or using a free-text field with an internal convention.
Q: What happens if the field is not marked as required and a user leaves it blank?
A: An empty value is valid when the field is not required in the project configuration. No error will be shown and the issue can be saved normally.
Q: Why is the plugin now called "Admin Essentials"?
A: Starting with version 1.0.0, the add-on officially adopts the name Admin Essentials to reflect its nature as a multi-module suite of utilities for Jira administrators. The first release includes the Email field; future releases will add new modules under the same package.