sbroshar , no one can be expected to know everything that goes on about everything, or anything.
However, when you "Create" a new issue, there is a warning that appears, "Please read our Jira guidelines before creating an issue." which does offer some suggestions before creating a JIRA. It would seem that you chose to ignore those constructive suggestions, at least according to your remarks in JENKINS-64834,
"First off this tracking system for tracking sucks. What's up with all the 'read this' in red BS? and how the F am I supposed to know what component? " (talk about leaving a bad taste ...)
When creating an issue, after entering a "Summary", JIRA also attempts to search for similar issues to prevent duplicates and provide a reference (Any results will often point you to earlier issue reports if it’s really a bug) . The summary you entered ("master ... slave ... come on folks") produces a limited (poor) match of top 5 issues.
Searching "master slave terminology" indeed returns the latest EPIC JENKINS-65398 Terminology update for master, whitelist, blacklist, and
JENKINS-62709 Remove remaining usages of "slave" terminology, which has a link to the original JENKINS-31095 2.0: Jenkins terminology sweep, which dates back to 2015.
If you do indeed find any more offensive terminology, I would suggest the best thing to do is to create an issue and link it to either JENKINS-31095 or JENKINS-65398. You are also free to submit a PR with the corrections as well.