Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Create resolved service desk request

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.


Hi Jonathan,

are you using JIRA Server or Cloud? If you are using JIRA server you can use Power Scripts add-on as a post function to automatically resolve the issue:

Hope that helps?



Jack Community Leader Jul 05, 2017

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.. 

Thanks for the confirmation.  


Log in or Sign up to comment
Community showcase
Published in Jira Service Management

Announcing Jira Service Management!

Hello there Cloud Community members! Today, we’re thrilled to announce Jira Service Management, the next generation of Jira Service Desk. Jira Service Management touts advancements in IT service ...

1,485 views 17 33
Read article

Community Events

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

Events near you