| Issue Number | 4664 |
|---|---|
| Summary | [Summaries] Correct translation workflow date display |
| Created | 2019-09-11 12:58:42 |
| Issue Type | Improvement |
| Submitted By | Osei-Poku, William (NIH/NCI) [C] |
| Assigned To | Kline, Bob (NIH/NCI) [C] |
| Status | Closed |
| Resolved | 2020-03-19 17:25:16 |
| Resolution | Fixed |
| Path | /home/bkline/backups/jira/ocecdr/issue.249596 |
Please correct the Summary Translation queue workflow date when there is a change in status. Currently, when a status is changed for a summary, the summary is correctly placed at the end of the queue. However, the date does not change. It retains the original date the summary first made it into the queue.
The current behavior of the software is a result of ticket OCECDR-4504, which asked that the date element be made read-only. Just to make 100% sure we make the right modification to the software: if the status changes the date changes, but if the status is unchanged and any other field (such as assignee) is modified, the date is left unchanged. Right, ~oseipokuw?
In other words, if (for example) I keep the same status but reassign the task to someone else you want to keep the date that was set when the job was originally assigned to the first translator? Or should the date change if any field is modified?
I just spoke with Linda about this and the preference is to change the date only when the status changes. So, leave the date unchanged if any other field is updated.
Got it, thanks.
I think I've got it working the way you want it to (on DEV). If you try it out, I suggest only cursory testing to make sure I'm not way off the beaten path, because there are more Leibniz changes to come for this script, and you'll probably want to do the comprehensive testing at the same time once they're all implemented.
~oseipokuw: note that I have some related questions for OCECDR-4678.
Yes, this appears to be working as expected. We will do further testing when everything else is done. Thank you!
Verified on DEV. Thanks!
Verified on QA. Thanks!
From what I can see, this appears to be working correctly on production (not easy to tell, because most summaries seem to whip through the statuses very quickly, going from cradle to grave all in the same day, sort of like a fruit fly, but I did find a couple of summaries whose workflow straddled multiple days). Can you confirm, ~oseipokuw?
Elapsed: 0:00:00.001555