It would be nice if the json output could include the count of open (and closed) issues for the milestone. That way, I could use it to identify milestones that can be safely closed (past due, with no open issues).
Describe alternatives you've considered
The progressPercentage field is not sufficient for this use case. A milestone with no open or closed issues will show 0 progress, as will one with a non-zero number of open issues but no closed issues. The former is safe to close, the latter is not.
Describe the solution you'd like
It would be nice if the json output could include the count of open (and closed) issues for the milestone. That way, I could use it to identify milestones that can be safely closed (past due, with no open issues).
Describe alternatives you've considered
The progressPercentage field is not sufficient for this use case. A milestone with no open or closed issues will show 0 progress, as will one with a non-zero number of open issues but no closed issues. The former is safe to close, the latter is not.
Thanks for considering this.