Currently when an issue changes workflow, a change item is added, eg.:

I think this is not a good idea.

Conceptually: the workflow belongs to the project/issue type, not individual issues. Why log changes of applicable workflow, and not change of applicable permission scheme, notification scheme, or issue type scheme?

In practice: there are various disadvantages:

• Messing with the issue history causes the 'Updated' date to be changed. Lots of people already complained about this and we 'fixed' it (JRA-7831).
• It simply fills the change history with useless information.
• It is a very mild form of security leak. When creating a workflow I never expected its name to be visible to customers.
• it appears in email notifications when issues are moved to a project with a different workflow. Eg. here is a support notification that went to a customer:

       [ https://support.atlassian.com/browse/CSP-18798?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
  
  Jeff Turner moved JST-172 to CSP-18798:
  ---------------------------------------
  
      Customer Status: Unknown
             Workflow: Support Workflow v.20  (was: Support Workflow - awaiting fix branch - v.23)
                  Key: CSP-18798  (was: JST-172)
              Project: Confluence Support  (was: JIRA Studio Support)
  ...
  

The workflow change is just confusing and irrelevant to customers.

So overall, logging the workflow change is a bad idea in concept and also in practice.