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

**URL:** <https://discuss.circleci.com/t/using-worflow-job-reference-in-another-jobs-requires-field-when-job-has-name-field/54012>\
**Category:** Build Environment\
**Tags:** workflow\
**Created:** [August 27, 2025, 9:51am UTC](https://discuss.circleci.com/t/using-worflow-job-reference-in-another-jobs-requires-field-when-job-has-name-field/54012 "2025-08-27T09:51:00Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamaciag](https://sea2.discourse-cdn.com/circleci/user_avatar/discuss.circleci.com/jamaciag/32/36618_2.png) [@jamaciag](https://discuss.circleci.com/u/jamaciag)\
**Post date:** [August 27, 2025, 9:51am UTC](https://discuss.circleci.com/t/using-worflow-job-reference-in-another-jobs-requires-field-when-job-has-name-field/54012/1 "2025-08-27T09:51:01Z")

</div>

Hello!

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

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

```

Will produce the following error:

```auto
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?