Comment 3 for bug 1400829

Jason, I believe that consensus (from past developer meetings) was not to make significant changes to the existing XUL staff client while the web client work was underway. Or at least, not unless changes were being made to both interfaces accordingly so that feature parity would exist. So yes, your assumptions are correct.

Even though it seems that adding the new functionality without any way for end-users to access it via the client seems strange, I'm not opposed to the addition of the code as seen fit by the rest of you. Not everything has to be immediately relevant I guess.

Needs to have a release note though, since we're adding new permissions to the system, along with a corresponding entry that says that this only applies to the back end for now, until such time as new interfaces are coded up?

Others are free to weigh in on this issue.