Created vs Resolved chart is showing zero resolved

[Vaibhav Bansal]

Hi,

While creating the report  "Created vs Resolved " it is showing zero as resolved.

while checking the filter of that report, Jira is showing unresolved in Resolution field for Resolved tickets also,

I don't know whether it is creating this issue or what? if yes, plz help me to rectify it!

Thanks,

[Max Foerster - K15t]

Hi Vaibhav,

can you please make sure to set a resolution when closing issues (post function)? Because without a resolution value in that field Jira will treat this issues as unresolved no matter what their status is (Done, Cancelled etc.).

Best, Max

[Vaibhav Bansal]

Hi, Max

Thanks for quick response, I'd attached the screeshot of the filter.

how can I change the resolution status?

[Max Foerster - K15t]

Hi Vaibhav,

you're mixing up to topics here. Status and Resolution. For Jira the resolution field is the source of truth to treat an issue as resolved or not. So depending on your workflow just make sure to add a value to the system field Resolution automatically or present a screen to users with the field on it to have them select a value. Unresolved on your screenshot just means "no field value". 

[Vaibhav Bansal]

Ok, thanks 

So from now onwards I have to give users an option to select value for resolution field, 

but for ticket already closed or resolved, how can I change the resolution field from unresolved, so that I can generate the correct report?

Thanks again for your help.

[Max Foerster - K15t]

Hi Vaibhav,

you can also automatically set a resolution value. Just add the "Update issue field" post function to the transitions and set a value for the resolution field. Or on boards using a simplified workflow check "Set resolution".

Keep in mind to clear that field value as well when re-opening an issue. If you want to update your old issues I suggest using a global transition to "bulk edit" the field value.

Best, Max

[Marc Isikoff]

Not everyone has access to Post functions - some installs are corporately maintained and thus we cannot.

[Thomas Adams]

Should you set the resolution to "Fixed" or to "Done" to show as "Resolved"?

[Max Foerster - K15t]

Any selected value will show as "Resolved". So it doesn't really matter. :)

[Thomas Adams]

@Max Foerster - K15t thanks for your reply. 

Also do you know a solution to the following problem:

I want the resolution date/time to be the date/time the issue was set to status "Merged" (which is basically our Done/Fixed/completed status), not the date/time of running the bulk change of the resolution - because then all the issues will have the same "resolved" date (at the time i do the bulk change) which makes all the reports wrong. 

If I run them through a bulk transition change, it will update the date/time for when the "Merged" status was set to the time I run the bulk transition. 

So my question: is there any way to set the resolution of all my merged issues to "Resolved" without creating a change entry (date/time change).

Any suggestions?

[Max Foerster - K15t]

@Thomas Adams , I'd say the only solution to prevent those connected changes to fields and the resolution date is to go through the database and directly edit the resolution value for the issues.

[RNV]

Hi @Vaibhav Bansal

Hello, if you have scriptrunner you can update the resolution field with a tool that this app.

anyway, I recommend you modify the transitions to update that field and so do not have this problem again

[Thomas Adams]

I tried to run the Bulk Fix resolution from Scriptrunner, but it looks like it no longer does what you pasted above. The text "without creating a change entry" has been removed from Scriptrunner.

I want the resolution date/time to be the date/time the issue was set to status "Merged" not the date/time of running the bulk change - because then they will all have the same resolved date (at the time i do the bulk change)

Any suggestions?