Do you recommend overriding the fields filled in the original request form by the customer such as the type of problem, priority, etc. or do you create duplicate fields and update the real information in them?
Generally speaking I would not create duplicate fields. I think changing the request type is fine. the priority is a bit more sensitive but if you have a clear policy on priorities then I think it’s fine to change the priority as well. However if you feel that sends the wrong customer message then consider creating a new field maybe severity.
Just as an opinion of my own about priority, I would never let a customer set the priority directly.
What they could do is choose an impact or/and an urgency of their ticket and based on that the agents will calculate automatically/set the priority.
But even there it's tricky because what is high or medium? I'm sure any user will find their issues to be critical/high. So proper communication about your urgency/impact matrix will also help.
other than that, I second @Jack in overwriting the fields and not duplicating them. If they were categorized wrong you should be able/allowed to rectify that.
(this does not mean play with the values to avoid SLA breach :))
This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events