I love the blue print idea.
Create ticket stages, and transitions.
However, it adds stages to my regular ticket stages which just makes the choices confusing for our technicians.
We have about 5 general daily stages for any ticket.
However, in order to complete a blueprint we have to create all the possible stages a ticket could use for a particular "process" such as onboarding.
I understand you have to have the stages for that particular process but it just makes the UX for technicians more confusing to have so many stages used in daily tasks.
Is it possible to hide blueprint stages from regular ticket selection? In other words, particular stages would only be possible by assignment from a blueprint action?