Hi, I wanted to check with the community on what is the best practice they have used. If you have both email support and raising request on the portal, have you tied both to the same project or kept them as different projects?
Requests raised by email have to be mapped on to a request type. I usually set up a dedicated request type for incoming email, one which has no mandatory fields (then hide it from the UI users).
I quite like the politeness of customising the "thanks, we've got your request" email with a line that says "we may need more information before we can proceed, we'll let you know if we do", then your people know to expect questions so your agents can flesh out the fields that would usually be mandatory.
No problem, but please do not assume this is the "right" answer.
It is, for a lot of people, but it does not fit every case universally. I think you already are doing what I want to recommend - go talk to the people who use your system.
As a consultant, I could write/talk a ton of stuff about best practice with a lot of software from many vendors. I am biased towards Atlassian stuff of course, it's my main field of expertise, but I still come back to the basic guideline - "best practice" is really "what works best for your people"
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
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