Quick command vs epic view inconsistency when adding an issue to an epic it already belongs to
Summary
This happens when an issue belongs to an epic and a user tries to add it to the same epic.
When the user tries that from the issue using quick command /epic
they get success response.
When the user tries to add the issue from the epic view, they get "We can't find an issue that matches what you are looking for."
We should be consistent. I suppose we should return an error (more meaningful than now - but that could be part of #32557 (closed)) for both cases.
Steps to reproduce
Issue view
- go to an issue that belongs to an epic ("Issue 1" that belongs to "Epic A")
- comment with quick command that assigns the issue to the same epic as it belongs
/epic [Epic A]
- you will see a success message
- the epic stays the same
Epic view
- go to an epic with some issues
- try to add an issue that already belongs to the epic
- You'll see an error message, nothing changes
What is the current bug behavior?
You see a success message for quick command but error for adding an issue from an epic
What is the expected correct behavior?
You should get a meaningful error for both cases