nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Created vs Resolved Report now showing Done items

simon.bate

Hi,

I am not seeing work items in the above report. Please can you suggest whilst this is not the case?

My current ticket workflow includes a "Done" selection, however my Kanban board settings currently has Done as an unmapped status.

All covered in the attachments.

Thanks Created vs Resolved 27th Feb.PNG Board Settings.PNG

Accepted answers

Merve Nur Bas

Hi @simon.bate

add a post function "Update issue field" to the transition All --> Done and All --> Rejected and add a resolution that suits.

Already existing issues need to be transitioned again (maybe via bulk edit?).

My best

Merve

simon.bate

I am still a bit confused @Merve Nur Bas to be honest but thanks for coming back to me

All comments

Ismael Jimoh

Hi @simon.bate ,

The created vs resolved tickets uses the following fields:

Created date
Resolved date
Resolution field

If your done status does not include a resolution then JIRA does not consider the ticket resolved because the resolution is empty and the resolution date is empty.

Hope this helps.

Ismael Jimoh

Also looking at the above, you have not mapped the Done status to the last column and this column for the board is the one it uses for considering a ticket is Done(for the board).

The resolution is still more important though.

simon.bate

Hi @Ismael Jimoh - thanks for the speedy reply.

What does the below mean please?

If your done status does not include a resolution then JIRA does not consider the ticket resolved because the resolution is empty and the resolution date is empty.

simon.bate

@Ismael Jimoh How is the Resolution date and field populated? Thank you

Merve Nur Bas

Hi @simon.bate

add a post function "Update issue field" to the transition All --> Done and All --> Rejected and add a resolution that suits.

Already existing issues need to be transitioned again (maybe via bulk edit?).

My best

Merve

Merve Nur Bas

I am not sure whether that works in cloud the same way though.

simon.bate

I am still a bit confused @Merve Nur Bas to be honest but thanks for coming back to me

Merve Nur Bas

We can surely try to solve the confusion. What causes it?

simon.bate

Thanks @Merve Nur Bas , i am struggling to understand what triggers the Resolved date and Resolution field from being populated? I have tried adjusting Kanban Board settings to bring the "Done" status into a mapped column but that didnt work i.e reflect as a resolved ticket in the Created vs Resolved Report.

Merve Nur Bas

Well I can only assume the following... When you look into the settings of default workflows, at least in Jira server, you will see that there is already a post function (things Jira does after the transition of the issue) which sets the resolution to a predefined one.

When I add a "closing status" (the green ones) to a workflow, I always need to add this post function manually. It just does not add this function automatically.

Assuming that your workflow is self designed, you will need to add the post function manually. It is possible that you do not have the according rights to do so.

Try to open the workflow and edit it. Click on the "All" arrow which leads to Done for example. Do you see a screen popping up on which you can navigate to the conditions, triggers, validators and post functions? If not please ask your system admin to edit this workflow for you.

If you can see it, please navigate to post functions --> add post function --> update issue field--> select resolution --> select from the dropdown menu which resolution it is. For example Done or whatever you chose.

After you add the post function you will need to make sure that this newly added one is on the bottom of the list. There are arrows to sort it to the end.

That should work fine. Afterwards you need to do the same for Rejected. And also make sure you transition the already existing issues to Done or Rejected again. They won't update automatically after changing the workflow.

Annddd also do not forget to publish the workflow.

Hope this helps.

My best

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud