139 votesRoman commented
Specifying midnight always requires extra concentration and careful double-checking. You probably don't realise how unnatural this is for someone who didn't grow up in a 12-hour time country. Please implement this!
15 votesRoman commented
It really is painful to manage a large number of variables for tenanted deployments, and adding the ability to filter project variables by tenant would address this more or less fully for our scenarios.
Here's a really common scenario for us: a variable is the same for all tenants, but different for each of the four environments. So we create it as a Project Variable. It's perfect. Just four entries to manage on one simple screen.
Now we want to override it for just one out of 8 tenants' Prod environment. What would be epic: just add another value, specific to Prod + this tenant. We'd end up with five entries, still super easy to manage.
What we have to do instead: add it to project variable templates, then paste the three per-environment values into 8 tenants, and the prod value into 7 tenants. Or define 4 new project variables, one per environment, to reference from all the tenants. Either way it's extremely painful.