How Does The Backlog Refinement Work?

Hello!

The TW-6439 (custom parameters in trigger context) is actually planned as per the roadmap for 2020 development: https://blog.jetbrains.com/teamcity/2020/03/teamcity-2020-roadmap-part-1-of-2/

Generally speaking, we do not base on the votes as a deciding factor for choosing what will be picked for the current development. Sometimes, a feature would require some extensive changes into the product core, and it may be postponed until we have a group of requests that could be analyzed together so to find the best approach for the refactor. For instance, conditional build steps feature (https://youtrack.jetbrains.com/issue/TW-17939) which is also on the roadmap was released as part of 2020.1 - the request has been registered on our tracker 9 years ago, but finally we have delivered this feature. As I can see, many of the smaller requests that are fitting well into the current scheme are being developed shortly after initial discussion so to prevent backlog growth altogether.

I can see the logic behind what is being chosen for the development may be non-transparent, but we do keep an eye on the most popular features (and it is a major factor for making a decision), so it is definitely worth to vote/comment for them, even if the development takes a while.