(JIRA/Azure) Board Columns for Testing?

[kristof (Kristof Van Kriekingen)]

@conrad.braam

I have the same pain @kristof has, two of our teams, by necessity, have such a different workflow that people forget what each ticket state means. It often feels like getting teams to work together is better served by duplicating and “linking” tickets across projects, to make this easier to track on everyone’s board when a ticket needs to move from one team over to another - but that kinda brings me to a discussion as to who is your customer when you do an internal delivery. Once again a #BikeShedding danger area.
For me, less columns wins every time, and better ticket descriptions that remove implicit knowledge.

<3 I also prefer the less is more approach for columns but how do you handle reporting, one of our metrics were:

• How long it took for a ticket to get from dev to test
• How long a ticket would be in the state " code review"
• How many times a ticket went back and forth

These are just a few of the metrics that they wanted to see.
Would you use custom fields then for some states or other things if you were to report on these things?