UX improvements to `Autocomplete of adding issues and adding epics to epics`
Problem
How can we build upon and improve the experience of adding related Epics and Issues (separately) while taking into account the thoughts in duplicated issues such as #10967 (closed) and #12259 (closed).
This issue will close the aforementioned issues and build upon #9126 (closed)
Solution
This design proposal will be slightly different for epics vs issues now due to the development of #2035 (closed). Epics will have the flow below. Issues will have a similar flow but will also include the radio button prompt for selecting between Related to, Blocking and Blocked By.
In the event that the user pastes in a URL, the system should be smart enough to detect as such and not initiate a search field.
User is prompted to search for epic or issue, depending on what they've selected.
On click of the input, the user is able to access the epic or issue dropdown list and add one or more of that asset type. The epics tokenize in the input as they add.
User sees the tokenized list of epics or issues they would be adding and clicks "Add" to include them in the list
## Proposal
* Do not require the user to enter the precursor of `#` or `&` before searching for an issue or epic to add. The user should be able to just start typing the issue or epic's `number`,`title`, or `link`
* Considerations here:
* What is the `link` behavior here? Does the search dropdown not trigger if a link has been pasted in (similar to current), or does it trigger and have that epic/issue first and focused, ready to be selected?
* How might we make this consistent with the experience of adding epics to an issue via the sidebar?
* Update the hint text to indicate to user that they can now search. Example (not final copy):
Adding issue | Adding epic |
---|---|
Edited by Holly Reynolds