Skip to content

Edits to Multi Environment docs#2712

Open
russell-loube-mixpanel wants to merge 3 commits into
mestopinal-multi-environment-docsfrom
russ/multi-env-docs-edits
Open

Edits to Multi Environment docs#2712
russell-loube-mixpanel wants to merge 3 commits into
mestopinal-multi-environment-docsfrom
russ/multi-env-docs-edits

Conversation

@russell-loube-mixpanel
Copy link
Copy Markdown
Contributor

Suggested edits to your Multiple Environments section in #2706. Open against your branch so you can review and merge into your PR if you like the changes — or cherry-pick parts.

Summary

  • Added an intro blurb framing the feature's value (dev/staging/prod environments for the same experiment/flag)
  • Fixed location: the selector is under the Configuration tab in the More section, not Settings
  • Clarified "Pushing changes" — now explicit that changes flow from the source/original to the linked destination
  • Rewrote "Duplicate To Project" to describe the actual UI path (overflow ... menu → Duplicate → choose destination), and clarified the same-project case
  • Experiments page: added Mixpanel-flag vs third-party-flag distinction — Mixpanel flags must be duplicated via the experiment's Duplicate flow; third-party flags let you duplicate the experiment directly
  • Feature Flags page: noted that experiment-type flags can't be duplicated from the Feature Flags page (matches the "You cannot duplicate an experiment type feature flag" tooltip)
  • Tightened copy and fixed typos throughout

Test plan

  • Read the rendered diff on the preview deploy and confirm it matches the actual UI
  • Confirm the Mixpanel-flag vs third-party-flag duplication behavior I described is accurate

🤖 Generated with Claude Code

- Add intro blurb framing the dev/staging/prod use case
- Fix location: Configuration tab > More section (not Settings)
- Clarify push direction (source/original -> linked destination)
- Document the actual Duplicate UI path (overflow menu)
- Note Mixpanel-flag vs third-party-flag duplication behavior
- Tighten copy and fix typos

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@russell-loube-mixpanel russell-loube-mixpanel requested a review from a team as a code owner May 19, 2026 20:01
@russell-loube-mixpanel russell-loube-mixpanel requested review from santigracia and removed request for a team May 19, 2026 20:01
@vercel
Copy link
Copy Markdown

vercel Bot commented May 19, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment May 19, 2026 9:48pm

Request Review

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
#### Feature Flags

If an experiment is linked to a Mixpanel Feature Flag, you can manage both from within the Experiments "Other Environments" menu.
If an experiment is linked to a **Mixpanel** Feature Flag, the underlying flag cannot be duplicated on its own from the Feature Flags page — use the experiment's Duplicate flow to copy the experiment and flag together. If your experiment uses a **third-party** flag instead, you can duplicate the experiment directly; no flag duplication step is involved.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Currently a user can duplicate the flag on it's own if they want to. But they are also able to duplicate both from the experiment page

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.

Interesting — in P3 I'm seeing the Duplicate button disabled on experiment-type flags with the tooltip "You cannot duplicate an experiment type feature flag" (screenshot below).

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.

Screenshot 2026-05-19 at 4 39 02 PM

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Gotcha. Yeah in this case we should probably match the existing flow.

Are you good with me just disabling the "Duplicate to Project" button in the Other Environments selector and displaying a tooltip with the same copy writing here?


This flow is for duplicating across projects only — to duplicate within the same project, use the same **Duplicate** option and leave the current project selected (this is also the standard in-project duplicate behavior).

Note that flags created as part of an experiment (experiment-type flags) cannot be duplicated from the Feature Flags page — duplicate the parent experiment instead, which will optionally duplicate the linked flag with it.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This is not currently true, although we could add this restriction. It may need some UX work though (I'm imagining the Multi Env selector just shows a redirect message to the experiment page instead of the normal multi-env content). Or we just hide the button altogether and replace with a link to the experiment tab.

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.

Same topic as the experiments.mdx thread — see screenshot there.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Copy link
Copy Markdown
Contributor

@santigracia santigracia left a comment

Choose a reason for hiding this comment

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

LGTM!

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