GenericTransfer reference not clickable in templates documentation

[Ajay9704]

What do you see as an issue?

The reference to airflow.providers.common.sql.operators.generic_transfer.GenericTransfer in the templates documentation is not clickable, even though other operator references on the same page are correctly linked.

This is visible on the main templates reference (https://airflow.apache.org/docs/apache-airflow/stable/templates-ref.html)

On that page:

References like airflow.providers.standard.operators.bash.BashOperator are clickable
But GenericTransfer appears only as plain text, with no link to its documentation

Context

GenericTransfer lives in
airflow.providers.common.sql.operators.generic_transfer

It is referenced in the templates documentation, but Sphinx does not generate a link
(likely due to missing or incorrect cross-reference resolution)

This is similar to the earlier issue reported for BaseSensorOperator (#60185), where the reference was also not clickable because Sphinx could not locate the actual module

Impact

Users cannot navigate from the templates documentation to the actual GenericTransfer class
Documentation becomes inconsistent: some operators link properly, others do not
It makes it difficult for users to inspect available template fields or operator parameters

Solving the problem

This appears to be another cross-reference resolution issue similar to the previous BaseSensorOperator case.

A likely cause is that Sphinx cannot correctly resolve the module path during documentation generation.

The fix may involve:

Ensuring that the provider module path
airflow.providers.common.sql.operators.generic_transfer
is included in the documentation build system

Confirming that autoapi generates documentation for that module

Verifying intersphinx mappings and any overrides in
devel-common/src/docs/provider_conf.py

Making sure the module is not excluded by filters such as autoapi_ignore or docstring-processing rules

Anything else

This appears to be the same class of problem reported in:

Issue #60185 (BaseSensorOperator non-clickable reference)

I looked into this while debugging the BaseSensorOperator issue and noticed similar symptoms.
This might indicate a broader cross-reference / provider documentation configuration gap.

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.