User stories/Tickets has been a common theme, Im curious if this work is exclusive to specific set of actions or if you are constantly are having to respond with different sets of data like specific testing notes, PR comments, etc. ?

In most instances you could fill out the story/ticket with successive paragraphs from War and Peace and not one person would ever notice. Mgmt. wants their "required fields" to be non-empty, but not one manager ever checks the actual content of those same fields. And the only report they ever pull to look at is the report of "X is missing content in field Y" report.

I definitely can see the point you are drawing at here, but In cases of code review, testing notes, PR comments - which typically is the bulk of the work in tickets for programmers (-mind you if your team has a PM) this is just not feasible. lol :)