web client has different process than Eclipse client?
We are on 2.0.0.2 and almost exclusively use the Eclipse client. We have a Process Configuration that forces a change set delivery to have a comment and associated work item. We recently had a developer play with the web client, and he was able to deliver a change set without a comment and an associated work item. I was a bit shocked at that, the process configuration does not seem to apply to web clients. I opened the Process Configuration, and noticed that there are two Deliver operations, one labelled "Deliver (client)" and the other "Deliver (server)". We have a process defined for the client one, but nothing for the server.
What is the difference between "Deliver (client)" and "Deliver (server)"? Is "client" for the Eclipse client and "server" is for the web client? |
One answer
This is a known issue. The process advisors aren't hooked up with the web UI at the moment. There is an open work item (I forget the # and jazzdev is down at the moment).
The difference between "client" and "server" is that the process advisor either runs on the client before making a call to the server or letting the server enforce the process. We are on 2.0.0.2 and almost exclusively use the Eclipse client. We have a Process Configuration that forces a change set delivery to have a comment and associated work item. We recently had a developer play with the web client, and he was able to deliver a change set without a comment and an associated work item. I was a bit shocked at that, the process configuration does not seem to apply to web clients. I opened the Process Configuration, and noticed that there are two Deliver operations, one labelled "Deliver (client)" and the other "Deliver (server)". We have a process defined for the client one, but nothing for the server. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.