Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Relocate feature flags from explore into issue details #12452

Closed
codyde opened this issue Jan 23, 2025 · 4 comments · Fixed by #12453
Closed

Relocate feature flags from explore into issue details #12452

codyde opened this issue Jan 23, 2025 · 4 comments · Fixed by #12453

Comments

@codyde
Copy link
Contributor

codyde commented Jan 23, 2025

Which part? Which one?

Feature Flags

Description

We should move the feature flag section out of Product walkthroughs > Explore and into the Issue > Issue Details section. This will match where FF context will live long term, match the product, and how you'll be able to search FF in the future.

Suggested Solution

Relocate the nav menu item to the issues > Issue details section, specifically for the general docs.

@getsantry
Copy link
Contributor

getsantry bot commented Jan 23, 2025

Auto-routing to @getsentry/product-owners-issues for triage ⏲️

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Jan 23, 2025
@codyde
Copy link
Contributor Author

codyde commented Jan 23, 2025

Note - this request came from Sasha / Jasmine.

@codyde
Copy link
Contributor Author

codyde commented Jan 24, 2025

Note PR submitted - #12453

@getsantry getsantry bot moved this to Waiting for: Product Owner in GitHub Issues with 👀 3 Jan 24, 2025
@codyde codyde linked a pull request Jan 27, 2025 that will close this issue
1 task
@codyde
Copy link
Contributor Author

codyde commented Jan 27, 2025

Update has been merged

@codyde codyde closed this as completed Jan 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants