| Issue Number | 356 |
|---|---|
| Summary | [Home Page] Document Activity Feed Shows Summary Posted by Peds Board Member |
| Created | 2016-01-08 09:53:47 |
| Issue Type | Bug |
| Submitted By | Juthe, Robin (NIH/NCI) [E] |
| Assigned To | |
| Status | Closed |
| Resolved | 2016-05-27 12:04:46 |
| Resolution | Cannot Reproduce |
| Path | /home/bkline/backups/jira/oceebms/issue.176800 |
This is a strange issue, but Melissa Hudson on the Peds Board uploaded a Late Effects summary this week and it is showing up in the Document Activity Notification Feed for Board managers who are not associated with the Peds Board. (Victoria, Robin B, Robin J, and Val are all seeing this message.) Any idea what could be happening? This is on PROD.
Her update also does not list the name of the summary but instead says "Melissa Hudson posted [message:field_title]. 01/07/2016"
(We were able to tell it was the Late Effects summary by looking at recent uploads on the Manage Documents page.)
This appears to be the packet Melissa was posting her summary to: Late Effects of Treatment for Childhood Cancer (January 2016) [Packet #15097]
I've done as much preliminary investigation as I think would be
prudent without having the ticket in the iteration we're working on
currently, just to make sure it wasn't something which should be dealt
with as an emergency. I still don't fully understand exactly what
happened, but it looks like the sort of situation which occurs when the
user gets impatient and bangs away at the same button repeatedly. In
this case, the user was posting the same updated summary, and the
multiple requests sort of stumbled and tripped over each other, with the
result that one of the notification message rows ended up with no title
or individuals to whom the notification was to be shown. The lack of a
title is what caused the [message:field_title] placeholder
to appear, and the lack of specific individuals to whom the notification
should be displayed resulted in it being displayed to all the board
managers. In any case, it seems unlikely to be something that would
happen frequently (this is the first occurrence, as far as I know), so I
think it's safe to let the ticket sit in the backlog for now while we
concentrate on the release tickets. Let me know if this doesn't seem
like the right approach.
Thanks for investigating, Bob. I completely agree - just thought we should report it since it's such a strange circumstance. I do not recall seeing this before, either. It appears she tried to upload the doc 3x, so your theory about the requests tripping over one another makes sense... Sharon got all three in her feed and in the packet. It's fine to keep this in the backlog. I'll let you know if we encounter it again or it becomes more urgent.
Closing this issue since it hasn't happened again. We'll reopen if it comes up again.
| File Name | Posted | User |
|---|---|---|
| screenshot-1.png | 2016-01-08 09:54:21 | Juthe, Robin (NIH/NCI) [E] |
Elapsed: 0:00:00.000691