CDR Tickets

When you view the report logged in with sufficient privileges (rather than as guest as with the URL you give), the Admin Menu button does indeed take you to the Admin menu. I imagine the most rational change to make (if any) would be to detect that the current session doesn't have sufficient privileges for all the buttons displayed, and prune the button list to reflect that condition. That's not an approach taken anywhere else in the menu system, though, so if we do that here, we might want to consider a broader examination of the menu system, perhaps modifying the Controller class to perform that modified logic globally. I did actually consider whether it would be more appropriate to have a button for the Dev/Admin menu instead of the Reports menu, but (a) this is a report, after all, and (b) the Reports button is what is provided on PROD. We can revisit all these decisions in Leibnitz, though.

but (a) this is a report, after all, 

It's possible you can get to this report via the report menu and in that case I would agree with you that the Reports menu makes sense.  In the current case, however, I'm getting the report by going through the Publishing menu.  I had seen these buttons as a way to get back to the parent and the top of the menu branch.  Jumping to a different branch was unexpected.

and (b) the Reports button is what is provided on PROD. 

I don't see any buttons when I look at the PubStatus report on PROD.  We must be getting to this page using different paths.
https://cdr.cancer.gov/cgi-bin/cdr/PubStatus.py?id=17574

Yes, it would be nice to come up with a standard approach across the pages.  Leibniz, here we come. 🙂

This is what you will get when you follow the link I included:

Buttons modified on DEV (Admin replaced by Developer Menu and Reports Menu removed).

Verified on PROD.  Closing ticket.