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,009
Community Members
 
Community Events
184
Community Groups

Clear Resolution on Transition to another status

Current Flow:

technician performs work>marks ticket as "closed" and provides a resolution>transitions to resolved automatically after a set period of time

Use case:

sometimes a technician will believe they have fixed the issue, close it, then the customer responds later saying it isn't fixed or it's happening again.  in this situation, i want to reopen the ticket as long as it has not reached the "resolved" status.  

I have created a transition from the "closed" status to our "waiting for support" status as this is how i want it to function when the ticket is reopened.  however, the post function to clear the resolution field does not clear the resolution field.  I also saw in one post that the resolved field needed to be cleared as well.  I tried adding that post function as well without success.

Is there a better way to accomplish this?  Am I using the wrong statuses?  everything i have read points to this method.  

1 answer

1 accepted

2 votes
Answer accepted
Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 23, 2023

This should be pretty straight forward, here is an example of the post function from the default ITSM workflow that clears the Resolution field when moving from Resolved back to In Progress:

Screenshot 2023-03-23 at 10.38.03 AM.png

Just make sure that you set the Resolution field to None, that will clear it.

Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 23, 2023

And also make sure that resolution is not on the screen if you have one associated with the transition.

Capture.PNGCapture2.PNG

 

That is the workflow transition in the first image.  I set it up just as it was described in other articles.  The second image is showing that the ticket in question did indeed transition back to waiting for support but the resolution is still set.

Mikael Sandberg
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 23, 2023

Is that transition the only one that you have between Closed and Waiting on support? And waiting on support does not allow transition to it from any status?

Try this, make a copy of the workflow and then change the workflow scheme to use the new workflow instead of the original one. On rare occasions changes to a workflow is not fully applied when you publish it, so by using a copy of it and changing the workflow scheme you are forcing a re-index. 

Technically, "Waiting for Support" accepts transitions from all other statuses.  The one in question is the only manually configured transition.  The rest are just out of the box transitions when you select "allow all statuses to transition to this one"

@Mikael Sandberg thank you.  the re-index seems to have worked.  i ended up having to redo some of my validators and post functions but the issue seems to be resolved now.

Like Mikael Sandberg likes this

Suggest an answer

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

Atlassian Community Events