fix(spans): Set name based on transaction

[loewenheim]

When converting a transaction into a segment span, set the span's data.span_name field directly based on the transaction's name.

This has several downstream effects:

• When the segment span is converted to a V2 span, the name field will be set based on data.span_name, instead of being inferred from a combination of attributes. This means the V2 segment span's name will be the original transaction name.
• Later, in the segment enricher, the segment span's name is copied into each child span's sentry.segment.name attribute. This means that each child span's sentry.segment.name will be the original transaction name.

Fixes INGEST-905.

[linear-code]

INGEST-905

[Dav1dde]

I think that's worth a change log entry, this is a visible behaviour change.

[loewenheim]

I wanna call this a bug fix, WDYT @Dav1dde?

[Dav1dde]

Bug fix seems appropriate to me!

[gggritso]

👍🏻

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit d328d21. Configure here.}

[cursor]

Unresolved merge conflict markers in CHANGELOG

High Severity

Git merge conflict markers (<<<<<<< sebastian/span-transaction-name, =======, >>>>>>> master) were committed to CHANGELOG.md. This leaves the file in a broken state — both changelog entries are present but surrounded by conflict markers, which will render as raw text. The conflict needs to be resolved to include both entries cleanly.

 

^{Reviewed by Cursor Bugbot for commit d328d21. Configure here.}