Automatically assign milestone to issues entering development

Context

Once we moved to a more continuous way of working we’re quite detached from milestones, yet a lot of things in the company is based on those. To not make it a hurdle to our engineers I came up with an idea - because we don’t pre-plan whole monthly iteration, our milestones are rarely updated on issues (MRs are different as they must have milestones). Back-propagating milestone to issue might be problematic considering there is often 1:n relation of issue to MRs and not sure which one to pick.

Goal

Increase the accuracy of milestones assigned to Growth's issues.

💡 Idea

• Create a triage-ops reactive policy:
  • Once Growth issue is moved to ~“workflow::in dev” apply current milestone to that issue. (The issue may still be completed in later milestone, but at least it will be more or less accurately assigned rather than usual %Backlog)

Challenges

• Not sure if our triage-ops policies are aware of what’s the CURRENT_MILESTONE - if not this may be tougher to implement as we’d have to update it monthly to new hardcoded milestone.