We actually didn't account for this in the new recipe page design (it still doesn't show the recipe set ID anywhere). We should probably try and come up with somewhere good to put it.
This is in my opinion a regression from the old UI - I need RS ID for acking/nacking a result. But the only page I found it on is job page, which can and does usually contain more than one recipeset - it's easy to nak wrong RS by mistake.
Dear Ales, how do you typically waive results? Use the job page or the bkr client? In other words, do you typically copy & paste the ID or navigation or?
From the command line. Because I waive jobs produced by automation so I run it from the server the service sits on (WebUI would be more user friendly but I don't want to install browser there)
Hello, thank you for opening issue in Beaker project. This issue was marked with component "web ui". As we are not planning to address any further issues in current UI, due to technical stack and not being able to work with Python 3 codebase, I'm closing this issue as WONTFIX. New UI will be reimplemented within new versions of Beaker. If you have any questions feel free to reach out to me. Best regards, Martin <martin.styk>