Philosophy of issue tracking

While working on Codesophy project I am trying to refactor my vocabularies and make them more simple and consistent. Today I have an "issue tracking" tools like JIRA on the table. I understand the a historical nature of this term, but in my opinion "issue" is not a good focus. Change management sounds like a better alternative.

Accordingly to Wikipedia issue is a "unit of work to accomplish an improvement in a system". That is... change. And this term is more flexible. For example we can consider potential change (risk).

We can then review typical Backlog-In Progress-QA-Deliver workflow of agile methods and even Red-Green-Refactor approach in TDD through a more mature Plan-Do-Check-Act in change management.