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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,558,942
Community Members
 
Community Events
184
Community Groups

We need to be able to Auto-close a ticket during the "Create"

I need to know how to add a button or status row directly while creating an errand where we could "tick" close/resolved/done or something similiar as the errand is already handled in the phonecall and Done.

Today we have to create the errand, then go into que and find it and change status to "Done" manually and the increasing load of phonecalls makes this a bit hard to be able to handle for our employees.

Is this possible to do?

3 answers

Thanks , yes we need to discuss this but I dont think we cant use this function

0 votes
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 04, 2023

Hi @Marcus Lindström ,

it sounds like your use case is that you are occasionally using the JSM project to log phone support. Moreover there is no effort required after simply logging the ticket. So given this you wish to have the ticket moved to Done as soon as it is created, assuming this is correct here is how I would approach the solution.

Use automation to move the ticket to done as soon as it is created. Here is automation rule concept:

  • Trigger - issue created
  • condition - use a label or custom field that is set during creation to check, e.g. Field condition labels contain "phone-support"
  • action - transition issue to Done

This I tried but problem is the "ticket" is not "removed" from que though status is changed to requested. We have DONE and SOLVED as status, so in order to close ticket we need to first mark as done and then solved. 

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 04, 2023

So why can you not transition to Solved in the automation rule?

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 04, 2023

If your workflow requires going thru Done before Solved transition twice or modify the workflow to allow direct to solved. 

Hi @Jack Brickey Jack, thanks for that but still even If i do first "Done" and then "Solved" it stays in the que. All other errands will be "removed" from que when "Solved", not sure what's causing this :)

0 votes
Tansu Akdeniz
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 04, 2023

Hi @Marcus Lindström 

Welcome to the community.

You can set issue status on create action. 

  • Go to Settings > System.
  • Select Edit Settings.
  • Turn on "Status: Allow users to select a status for an issue they're creating" option.
  • Select Update to save your changes.

Also check this page: Set the status of an issue while creating it

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Apr 04, 2023

Indeed this is a new feature however, I'm not a big fan of this as it is a system setting vs. project setting. My recommendation, before enabling, would be to check with all other project teams. There is a discussion/request to make this config project based. Just my $0.02.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events