Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Add "Resolution" to ticket workflow

Nick.corby
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 31, 2022

Hi all,

I've been searching for a while and haven't been able to find an answer - I'm in a team-managed Service project and want to be able to utilise the "Created vs Resolved" widget for team reporting. However, I don't seem to be able to add the "Resolution" field to any of my workflows, and the widget is currently showing 0 Resolved tickets for the period, which is incorrect:

2022-08-01 10_43_56-Window.png

Not sure what I'm missing? 

Thanks!

1 answer

0 votes
Mayur Jadhav
Community Champion
July 31, 2022

Hi @Nick.corby ,

Hope you are doing well!!

In your workflow, you need to add a screen for the Done, Cancelled, or Close transition in which you need to add a Resolution screen and make the Resolution field mandatory if you want sure users don't miss to field value while transitioning the issue to Done or Cancelled status.

And also post function to clear the Resolution field value if the users reopen the issue after closing.

Steps to Add Resolution field.

  1. Project Settings.
  2. Workflows.
  3. select the workflow, where you missing "Resolutions ".
  4. Edit.
  5. Select the Transition which is connected with "Done"
  6. place Resolution Screen.
  7. Publish Workflow

 Atlassian has created a very detailed document Please have a look at Best practices for using the "Resolution" field.

 

Hope this helps.
Mayur

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 1, 2022

A couple of minor warnings in here.

Do not make the resolution mandatory.  Mandatory fields have to be filled from the point of creation of an issue, and you really do not want to be creating resolved issues.

If you put the resolution on an editable screen (create, edit or transition), then the field will default to a value, which you can not clear.  So whenever someone uses one of those actions with a resolution on screen, they will resolve the issue.  You don't want that on create or edit!

So, that leads on to the second warning - the resolution field should never be added to create or edit.  It should be added to the screens Mayur mentions.  (We don't care about view, it's not an enterable screen and Jira displays it anyway)

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events