[MM-1121]: Fix epic selector not displaying options if field is renamed in Jira #1134
+28
−15
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Create Issue
modal had a bug: if theEpic
field in a Jira project was renamed to anything other thanEpic
, the dropdown for selecting Jira epics displayed no options.Epic
, and then checks if the filtered field matches the Epic field schema before fetching all epics from the project.Epic
. This PR removes the name-based check and instead relies exclusively on the field schema to identify the Epic field.Ticket Link
Fixes #1121
What to test