Make custom states possible

[thebspin]

Hi there!

We are in need of a workflow where during sprint work we can make changes to labels but not push these to production till the end of a sprint. But our client wants to make changes to labels without waiting for a deployment at the end of a sprint.

Right now we don't see a real convenient way to do so. While checking out the docs about content delivery i noticed that you can also do a manual sync based on your selection. Having more states would allow us to make a difference between labels that are approved and added during a sprint. And labels that the client them selfs can approve and publish them to production.

Any other idea of a workflow would also be appreciated.

[JanCizmar]

Hey! Have you considered using tags for this. When you add a new key in the development phase, you can tag it with tag draft or draft-<feature-id> and this way you can distinguish.

[thebspin]

Hi , I did take a look at tags but i don't see them being available to distinguish for content delivery. With tags it would be nice to tag something with feature-number for example and everything that is tagged with feature-* would not be run to prod s3 deployments for example.

[JanCizmar]

Looks like the backend currently supports single tag filtering (anyway, it isn't configurable via UI), however supporting multiple tags is not a big deal.