You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
When a user calls our help desk, we require our agents to fill out a ticket detailing the call. Usually, the user's issue is resolved on the call. Is it possible to create an issue in Service Desk that is already resolved? Currently our agents are creating a ticket and then resolving it which is an additional step for them.
I expect you can do this w/o a plugin if the following solution would be acceptable.
Create a unique Issue Type (Cust_Call)
Create a very simple workflow: Open to Done. You can do this simply by creating a new workflow, add Done status, move the transition from the default (New) to the Done, setup your post functions as you want, e.g. resolution = Done.
The user takes the call and creates a new ticket adding call notes in description and when call is complete it moves to done. If there is followup on this you could always use Sub-Tasks. If you want certain fields to be completed then simply create a unique create screen and associate to the Cust_Call issue type.
I thought about that as well. The only reason I was hesitant was that ideally I would have this request in the support portal for our agents to submit a Cust_Call request from there, but there isn't a way that I know of out of the box to prevent regular users from submitting that request. It still seems like your method is the best way to go.
Yep therefore you would need another addon to restrict request type visibility based on groups..