Your comments

I'd very much like this too.


My current workaround is to create 4 tasks (1/Jan, 1/Apr, 1/Jul, and 1/Oct) and have each of those repeat yearly. Not ideal though...


An option for biannually would be equally useful.

Is there any news on the bug I posted related to this?


Since this update the workspaces using now non-existent colours have turned white, however attempting to choose a new colour does not save properly. (Only until you refresh Redbooth, which needs to be quite frequent to keep up to date.)


The AJAX request looks like it does not include the project ID in the URL or POST data, so the Redbooth server may not know which project the colour should be persisted with.

Hi Claire,


It's not just you that were using this feature.


Our company used them to distinguish which workspaces were non-standard, typically because they were internal only (blue), or a workspace a client can also interact with (red).


I had filed support ticket with a question about this, and got the following response:


  • Yes, the change is intentional. Our Product team considers this change will bring a more consistent look across platforms. If you don't consider this change convenient, please submit your feedback in our forum so they can review it.


The option for an organisation do define their own custom colours would be the ideal option if the preset range is going to be this much narrower.