Issue Summary

Change from "issue" to "work item" has caused unintended replacement of the word "issues" when not referring to Jira Issues. This seems to have been done in bulk to replace the usage of the word "Issues" when referring to items within Jira to "Work Items", but was not double checked for context. As a result, places in Jira that used the term "issues" in a different context appears to have replaced that word with "work items", even though on context it is not referring to a jira issue. One example can be found when creating a For: JQL branch in automation, where disabling the option "Only include work items that have changed since the last time this rule executed" results in a warning that reads "May cause performance work items", instead of "May cause performance issues"

Also cases where changes have not occurred but where documentation seems to have been updated as though it has. In this case, the entire Issue settings menu at /jira/settings/issues/issue-types (consistent for all of the pages under /issues it seems and for the drop down settings menu)

Steps to Reproduce

1. Create an automation rule
2. add a "for related issues" branch
3. uncheck the option "Only include work items that have changed since the last time this rule executed"

Expected Results

The message would read correctly: "May cause performance issues"

Actual Results

The message reads "May cause performance work items"

Workaround

None. Suspect this is a widespread issue in any spot where the word "issue" or "issues" is used but not in the context of a Jira Issue