'Resolution Time'' and ''Closure Time'' Dataplane reports issue

[Deleted user]

Hello,

I am currently using ''Resolution Time'' and ''Closure Time'' Dataplane reports to determine the average time from status OPEN to CLOSED for project tickets.

The issue I have with the data is that, in my workflow, a ticket can go from status 'OPEN' to 'CLOSED' (cancelled resolution) without having been in status 'RESOLVED'. Therefore, the ''Resolution Time'' report has inaccurate data as it does not take those tickets into account. 

Also, I have tickets that follow the workflow as such : 'OPEN' - 'IN PROGRESS' - 'RESOLVED' and remain in status 'Resolved' for some time before going to status 'CLOSED' (and some never do!). So, data from the ''Closure Time'' report is also not valid because :
1) Tickets can remain in status 'RESOLVED' for weeks before status is changed to 'CLOSED' so my closure time is inaccurate.
2) Tickets in status 'RESOLVED' are not picked up by the ''Closure Time'' report when I'd want to consider them 'CLOSED' even if not in that status.

Is there a report (or JQL) I could use that would give me the REAL resolution time from ANY open STATUS to either RESOLVED or CLOSED? What would be your recommendations?

Thank you so much!

[Tuncay Senturk _Snapbytes_ · Accepted solution]

Hi Pupie,

I have created an issue about this. You can see and follow it via link https://bitbucket.org/tuncaysenturk/jira-enhancer-plugin/issue/55/jep-436-custom-field-does-not-work-with

Could you please provide me more info and attach screenshots in order to see where the problem is?

I am waiting for your response to solve the problem as soon as possible.

Regards

Tuncay Senturk

[pupie]

Hi, Please refer below screenshots:

1. The system language is set to SChinese as below.

2. I logged in to system as Admin and created a custom field then apply it to a default screen.

3. Then try to config its status range as below

4. Select value from the list and click save button. The page reloads but stay on it.

it will not return to parent page as it is shown in step3.

5. I have to navigate to the JIRA issue tab and goto its summary again to check whether the change is saved. But nothing had been changed.

I also noticed that alot of strings from JEP can not be translated by IPT(In Product Translation) Addons such as the "Reopening History" and "Stateoscop" tab added to issues summary page and the time value unit.

I can't add attachments to the issue you created since server always return 403 error when trying to attach file to that issue. I also confirm that the control "Amount time till resolution"works with localized settings.

[pupie]

(atlassian-jira.log)

Hi,

I just reproduced this issue on my laptop with brand new installation of JIRA 6.1.7.

I just install mysql 5.6.16 on Win7 x64 Ultimate English with language locate/code page/format switch to SChinese/PRC. then I install JIRA and SChinese language pack, Change jira language to SChinese, Download and install JEP to configure as screenshots I provided above.

[Tuncay Senturk _Snapbytes_]

Hi Pupie,

I have reproduced and fixed the localisation problem. In a few days version 4.3.7 will be released.

Thanks for your help

Regards

Tuncay Senturk

[pupie]

Hi Tuncay,

I just tried 4.3.7 on JIRA 6.1.7 and the old issue is gone.

but there are still some strings not translatable . such as status string and the time unit on the stateoscope page.

I also tried the custom field using :time amont till resolution" and there is no way to translate the time unit. Please refer the screenshot.

I think this could be a localization enhancement CR.

Stateoscope page:

[Tuncay Senturk _Snapbytes_]

Hi Pupie,

Thanks for your feedback. I have missed those fields and I have just created an issue about this. Please watch the issue.

Thanks

Tuncay Senturk