EBMS Tickets

~juther: Supriya finished her testing. As it turns out, CBIIT didn't follow our instructions, and as a result we ended up picking up Drupal 7.61, which was released right before the deployment (I warned them this could happen if they didn't use the commands I gave them instead of making up their own commands). So I upgraded QA to 7.61 and Supriya ran her tests again. The only thing she found (other than a console error message which has been around for months) is reflected in this ticket. I confirmed that the behavior described in this ticket it also present on STAGE, which is still at Drupal 7.60, so this isn't something which resulted from CBIIT's mistake. It's even possible that this behavior has always been present (perhaps it only happens when the queue is empty, and users didn't report it because they figured out that they can get the topic dropdown working by switching the board back and forth). In any case, whether it's behavior we've lived with for a while, or was introduced by the record core or module updates, we'll look into it as part of the next release. As far as we can tell, everything else looks fine. Let us know if you run into any anomalies, of course. Have a great weekend!

Thanks, Bob. Neither Victoria nor I have seen this before, but it could potentially be because we have default Board's assigned to us so the Board is pre-selected. In fact, I think anyone who views that page has a default Board, so this may not be an issue for us. We'll keep an eye out for this behavior, though.

Haven't noticed any other problems so far. Thanks, and hope you have a great weekend too!

I can no longer reproduce this behavior. The original description implies that when the page loads the board field already has a board selected. That is not the case when I load the page as Test Librarian, nor would I expected it to be. If someone can come up with a legitimate use case which does reproduce the behavior, we can re-open this ticket.