Using worflow job reference in another job's `requires` field when job has `name` field

Build Environment
1

Hello!

I found that using name field on a workflow job has an unintended effect. Consider the following workflow example:

workflows:
  xyz:
    jobs:
      foo_bar:
        name: Foo Bar
        …
      baz_qux:
        requires:
          - foo_bar
        …

Will produce the following error:

Job 'baz_qux' requires 'foo_bar', which is the name of 0 other jobs in workflow 'xyz'

The solution is to use requires: - Foo Bar instead. This is not explicitly stated in the documentation. Using the underscored references (or any other *case) is super convenient and less prone to errors. But having the names makes the workflows much more readable. I am curious if there’s any way to make it work. Or, are there plans to make it work?