Matthew Elwell
Matthew Elwell
Hi @predrag-nikolic-kombinat-dev , this does seem like odd behaviour (and I think is somewhat linked to the unclear documentation as mentioned in #99). From looking into the implementation, I am...
Thanks very much for providing the examples - we will look into these and get back to you.
Related to #6191
My understanding of the requirements, written in test scenarios. @kyle-ssg is this your understanding of the behaviour? Anything else that we should be testing? ## Non-scheduled CRs 1. User can...
> @matthewelwell The exception to that at the moment is anyone can edit a change request if they have the ability to create one. I can see a use case...
I've aligned the BE with my expectations in a PR [here](https://github.com/Flagsmith/flagsmith-workflows/pull/88).
@khvn26 @gagantrivedi is this superseded now by #6401 ?
We originally created a CodeArtifact repository (currently in eu-west-2) to host public packages (e.g. flagsmith-common), however, it appears that it is _not_ possible to make CodeArtifact repositories open to the...
As mentioned above, and discussed in a recent engineering meeting, it seems as though hosting the public packages in pypi (e.g. flagsmith-common) is still the best way forwards.
Since we migrated all task processor into flagsmith-common and published to pypi, this is less of an issue since there are no longer any dependency tree conflicts that we were...