> I also have never seen my #3 really done well because getting developers to keep issues up to date has always been difficult. This is where CI/CD integration

> I also have never seen my #3 really done well because getting developers to keep issues up to date has always been difficult. This is where CI/CD integration of tickets and good commit hygiene comes in, in my opinion. If your pipeline updates the state of the ticket as it progresses and commits are both sensible (describing the work completed rather than 'WIP: did stuff') and viewable from the ticket's history, that /should/ be sufficient to gauge progress when viewed alongside the work spec.