Skip to content

Document Campaign event ID display in the Campaign Builder#783

Open
promptless-for-oss wants to merge 4 commits into
mautic:7.2from
Promptless:promptless/campaign-event-id-display-7.2
Open

Document Campaign event ID display in the Campaign Builder#783
promptless-for-oss wants to merge 4 commits into
mautic:7.2from
Promptless:promptless/campaign-event-id-display-7.2

Conversation

@promptless-for-oss

Copy link
Copy Markdown
Contributor

Open this suggestion in Promptless to view citations and reasoning process

Adds an "Identifying Campaign events" section to the Campaign Builder docs explaining that saved Campaign events now always display their numeric ID (prefixed as "(ID: )") on event cards, the Campaign Preview, the Jump to Event action, and the Redirect Event drop-down. Documents that the ID disambiguates same-named events, which is especially useful when redirecting scheduled Contacts on event deletion. Reflects mautic/mautic PR #16103.

Trigger Events


Tip: Tell your friends working on non-commercial open-source projects to apply for free Promptless access at promptless.ai/oss ❤️

Campaign event IDs are now always shown for saved events (prefixed as
'(ID: <number>)') on event cards, the Campaign Preview, the Jump to Event
action, and the Redirect Event drop-down. This helps disambiguate events
that share the same name, especially when redirecting scheduled contacts
on event deletion. Reflects mautic/mautic PR #16103.
Identifying Campaign events
---------------------------

.. vale on

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR #16103 changes the Campaign event templates to always show the event ID for saved events. The (ID: <number>) prefix and the surfaces it appears on come from _generic.html.twig, _preview.html.twig, and jump.html.twig (each gates on event['id'] matches '/^\d+$/', so unsaved temp events show no ID), plus campaign-event-delete-modal.js, which prefixes the ID in the Redirect Event drop-down. The new mautic.campaign.event.id="ID" translation string confirms the displayed label.

Source: mautic/mautic#16103

Comment thread docs/campaigns/campaign_builder.rst Outdated
Address review feedback: 'Redirect Event' is the delete dialog's confirm
button, not a labeled drop-down. Describe the ID's location as the drop-down
used to redirect scheduled Contacts when deleting an event.
@promptless-for-oss

Copy link
Copy Markdown
Contributor Author

Good catch, thanks @adiati98 — you're right that there's no drop-down labeled "Redirect Event". I checked the source change in mautic/mautic#16103: that string (mautic.campaign.event.delete.redirect_event) is the confirm button in the delete-event dialog's footer, not a drop-down. The ID-prefixed options actually appear in the drop-down under "Redirect existing contacts scheduled for this event to another event:".

I've updated the docs to describe that drop-down by function rather than referencing a non-existent "Redirect Event" drop-down. The sentence now reads: "…and in the drop-down you use to redirect scheduled Contacts when you delete an event." Vale passes with no new warnings, and the change is pushed to this PR.

Comment thread docs/campaigns/campaign_builder.rst Outdated
@promptless-for-oss

Copy link
Copy Markdown
Contributor Author

Thanks @adiati98 — removed the colon. The sentence now reads:

The ID helps you tell events apart when two or more share the same name. This matters most when you delete an event, because the delete dialog asks you to redirect any Contacts scheduled for that event to another one, and the ID lets you pick the exact event you want from the drop-down.

Vale ran clean on the file. The branch has been updated.

@adiati98

adiati98 commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Hi @rohitpavaskar,

Can you please review the content in this PR and see if they're align with your changes in mautic/mautic#16103?

TIA! ✨

@rohitpavaskar

Copy link
Copy Markdown

Hi @rohitpavaskar,

Can you please review the content in this PR and see if they're align with your changes in mautic/mautic#16103?

TIA! ✨

Hi @adiati98,
Dos changes looks good covering all the work of PR.
Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants