Similarly to #31278, this context entry can be interpreted wrongly. Specifically, one redmine user did the following:

1. Opened an issue (issue#view) (redmine:3000/issues/40, for example)
2. Added a related issue (41, for example)
3. Decided to delete the relation
4. Opened the context menu, instead of clicking on the broken link icon (the one with the tooltip "Delete relation", but who reads tooltips?)
5. Clicked on the "Delete" button
6. Clicked OK on the popup (the text there could be more straightforward, for example: "Delete issue(s)? Are you sure?" but who reads popups?)
7. Later, called support (me) asking why the issue disappeared?

The problem is not the user not reading the popups. Various popus in Redmine are written like this: "Are you sure you want to" whatever. This is not the best way to write confirmation popups, but even with a strightforward text, lie in the example above, popups are rather dismissed than acknowledged.

The problem here is the usability of the context entry. The icon to delete the relation is next to the icon that opens the context menu, but "Delete" issue is more destructive than "Delete relation", because you can't rollback deleting an issue.

Notice that "Delete relation" though less destructive, because there is very little data loss, and you can always redo a relation, has the full text "Delete relation" on the popup.

I won't post a patch. Instead i did a grep of label_issues_delete (my sugestion, though it needs translation for other languages):

app/views/context_menus/issues.html.erb:152:  
<%= context_menu_link l(:label_issues_delete), issues_path(:ids => @issue_ids, :back_url => @back),

config/locales/en.yml:594:  label_issues_delete: Delete issue(s)

config/locales/pt-BR.yml:365:  label_issues_delete: Excluir tarefa(s)