Matthew Elwell

Updated to be a spike - outcome should be some smaller issues and a clearer specification of the work to be completed, which can be estimated and hopefully added to...

Converting to draft to: 1. ~Fix isort issues~ 2. ~Wait until I can bump to 1.0.0 (which requires an update in flagsmith-workflows)~

I have verified that there haven't been any more changes in the `task_processor` module in this repo. Once CI passes, I will merge.

The key issue described above is (1). There are a few options that we can investigate here for a solution: **1. Add an `alias` function to our SDKs which will...

I think for SaaS (more specifically the Edge API), we'd want to look into using DynamoDB streams to trigger a lambda which will update a new model in Django which...

I've begun investigating this a little further. I have made a start on some PoC code for option 2 in my comment above ([here](https://github.com/Flagsmith/flagsmith/issues/4016#issuecomment-2129180738)). See the WIP PR [here](https://github.com/Flagsmith/flagsmith/pull/4493). Some...

@kyle-ssg In this PR #4569 I have added a new field to the edge identities called `"dashboard_alias"`. From a FE perspective we need to 1: 1. Display it on the...

Re-opening to track being able to search by trait.

> @matthewelwell Question here, would we want that flag state to be in git? I guess that would be quite useful in a way (To see diffs). Either way this...

I don't fully know how it works tbh, but what I'd like to happen is that all users logging in to the Flagsmith dashboard in a self hosted installation that...