If you're troubleshooting an integration and wondering whether the integration user can view the same fields on the Jira Create and Edit screens for a particular Project and Issue Type, it's worth checking the following:
Why this matters
A common reason for issue creation or update failures is that a field is available on one screen but not the other.
For example:
- A field may be present on the Create screen, allowing an issue to be created successfully.
- The same field may be missing from the Edit screen, causing update operations to fail.
- In some cases, field configuration or permissions can further complicate the behavior.
How to verify
- Identify the Project and Issue Type involved.
- Review the Screen Scheme and Issue Type Screen Scheme associated with that project.
- Confirm that the required fields are available on both:
- Create Screen
- Edit Screen
- Verify that the integration user has the necessary permissions and field visibility.
A practical approach
If you're using an integration platform such as Sinergify, one useful step is to review the field mappings and validation information available within the integration. This can help pinpoint whether a sync issue is related to screen configuration, field accessibility, or permissions, rather than spending time digging through API logs.
Best practice
Whenever new custom fields are introduced, consider validating:
- Field configuration
- Screen configuration
- Permissions
- Integration mappings
before moving changes into production. It can save a lot of troubleshooting later, especially in environments with multiple projects and issue types.
Has anyone else run into cases where a field was available on the Create screen but missing on the Edit screen? What was your approach to diagnosing it?
