Details
-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
1
-
Severity 3 - Minor
-
Description
Issue Summary
Changes are being rolled out to the epic fields (relevant Community post), including making Epic Name an optional field. Going forward the Issue Summary will be used instead.
In the advanced issue search, to search for child issues of a particular epic the 'Epic Link' field is added to the criteria and the desired epic/s selected.
However, when entering the name of the epic only issues with a match in the Epic Name field are returned, epics with a blank Epic Name field don't appear as an option to select.
**The development team have already reproduced this bug and logged an internal development task to rectify it, this report is intended for Atlassian Support/Customer visibility.
Steps to Reproduce
- If Epic Name is already an optional field, create an epic with the Epic Name field blank and the intended name in Summary instead
- From the advanced issue search, in the Basic mode select '+ More' and choose the 'Epic Link' field.
- Type in the beginning of the epic summary - epics with an Epic Name that match will be returned, but not the intended epic.
Expected Results
Epics with matching text in either the Epic Name or Summary fields should be returned as options to select.
Actual Results
Only the Epic Name field is searched, and epics with a blank in this field are excluded unless the complete issue key is entered as the search value.
Workaround
These epics will appear as an option to select if you search for the full issue key of the epic, eg. ABC-1234. (Partial values don't return a result.)
JQL queries also work but only if the full key is provided.