Allow custom Issue Type selection for Jira Integration in Crashlytics
Description:
Currently, the Jira integration in Firebase Crashlytics is hardcoded to look for an issue type specifically named "Bug".
Many organizations, like ours, use customized Jira project schemas where the issue type for defects is named differently (e.g., "Anomalie" in French, or other custom naming conventions). Because of this hardcoded requirement, the integration fails to connect if a "Bug" issue type does not exist in the Jira project.
Request:
Please update the Jira integration settings to allow users to select their preferred Issue Type from a dropdown menu populated by their Jira project's available issue types.
This would greatly improve the flexibility of the integration and allow teams to maintain their existing Jira workflows without having to create redundant or unnecessary issue types just to satisfy Firebase's configuration requirements.
Related isssue: https://firebase.uservoice.com/forums/948424-general/suggestions/47540342-jira-cloud-integration-for-post-production-issue-t
Grégory Verron
shared this idea