CDR Tickets

Issue Number 4241
Summary [Translation Queue] Modify workflow management report to track history of changes
Created 2017-03-20 09:40:36
Issue Type Improvement
Submitted By Osei-Poku, William (NIH/NCI) [C]
Assigned To Kline, Bob (NIH/NCI) [C]
Status Closed
Resolved 2018-03-27 16:42:12
Resolution Fixed
Path /home/bkline/backups/jira/ocecdr/issue.205050
Description

Please modify the translation workflow management report so that we can retrieve the history of status changes. We want to have the ability to retrieve reports of status changes through the translation process.

Comment entered 2018-03-08 09:00:36 by Kline, Bob (NIH/NCI) [C]

Do you have any specs for this report? Or will you accept whatever I come up with?

Comment entered 2018-03-13 07:17:18 by Kline, Bob (NIH/NCI) [C]

will be providing specs for this report.

Comment entered 2018-03-20 13:26:35 by Osei-Poku, William (NIH/NCI) [C]

1. Please modify the report interface to include a new optional checkbox called “Include historical status changes)”.
2. Please add a new column to the report called “Translation Status History”
3. Please add a new column to the report called "Translation Status History Date"
4. Please add a new column to the report called “User”
5. All the new columns should be placed after the existing columns
6. When the checkbox is selected, include the historical sequence of translation status changes within the selected date range. For example, if a summary currently has a status of Translation Pending, report when it changed from Ready for Translation to Translation Pending in the “Translation Status History” column and report the date the change occurred in the "Translation Status History Date". For summaries that have had multiple changes, please record all the changes in the order they were changed from top to bottom.
7. If a summary has not changed status within the date range selected, still include the summary in the report but leave the “Translation Status History” column blank.

Essentially, as much as possible, we would want the report to work just as it is working now but the addition of the new checkbox and the three new columns that record all the history of status changes, dates and users for the summary that has been selected.

Comment entered 2018-03-22 10:15:07 by Kline, Bob (NIH/NCI) [C]

I'm not sure how it would work to have separate columns in a single row for multiple states. The user values wouldn't necessarily line up with the state values, for example. Also, the 7th item above doesn't match the way the report works now. I have implemented an approach on DEV which actually gives you more than you're asking for, by giving each state change its own row. Tell me what you think:

Comment entered 2018-03-22 14:56:47 by Kline, Bob (NIH/NCI) [C]

: I noticed while working on this ticket that the CGI script for managing translation jobs has never handled Unicode properly. Please strongly encourage your staff to report bugs when they come across them.

Comment entered 2018-03-23 14:17:47 by Osei-Poku, William (NIH/NCI) [C]

Can the report be sorted by Summary so that all the status changes for each summary are grouped under the summary? That would be similar to what we have for the Type of Change report.

Comment entered 2018-03-23 14:47:47 by Kline, Bob (NIH/NCI) [C]

Comment entered 2018-03-23 15:59:01 by Osei-Poku, William (NIH/NCI) [C]

Thanks!

Comment entered 2018-03-27 16:40:22 by Osei-Poku, William (NIH/NCI) [C]

Verified on DEV. Thanks!

Comment entered 2018-04-11 09:57:28 by Kline, Bob (NIH/NCI) [C]

[copied from OCECDR-4424, where this thread had somehow wandered]

I have adopted a slightly more flexible approach to the comment display, allowing you to control whether comments are displayed in full or truncated for either flavor (current or historical) of the report. This is on DEV. If you prefer, I will switch to the less flexible approach, and always truncate comments for the current jobs report and always display them in full for the historical report. After you have let me know your preference I'll deploy to QA.

Comment entered 2018-04-11 13:09:40 by Osei-Poku, William (NIH/NCI) [C]

This one looks great. Thank you! Please proceed to install on QA.

Can you do same for the Translation Job queue in a future release?

Comment entered 2018-04-11 13:42:57 by Kline, Bob (NIH/NCI) [C]

On QA.

https://github.com/NCIOCPL/cdr-admin/commit/4c784ea4

Can you do same for the Translation Job queue in a future release?

Not as straightforward doing it for the queue (since it's not a report generated from a form on which you are already specifying options), but I'm sure we could come up with something.

Comment entered 2018-04-11 15:16:26 by Osei-Poku, William (NIH/NCI) [C]

Okay. Thanks!

Comment entered 2018-04-11 15:16:44 by Osei-Poku, William (NIH/NCI) [C]

Verified on QA.

Comment entered 2018-05-09 15:52:11 by Osei-Poku, William (NIH/NCI) [C]

Verified on PROD. Thanks!

Attachments
File Name Posted User
screenshot-1.png 2018-03-23 14:47:21 Kline, Bob (NIH/NCI) [C]
Screen Shot 2018-03-22 at 10.04.45 AM.png 2018-03-22 10:12:08 Kline, Bob (NIH/NCI) [C]
Screen Shot 2018-03-22 at 10.12.30 AM.png 2018-03-22 10:12:54 Kline, Bob (NIH/NCI) [C]

Elapsed: 0:00:00.001456