|RE: [corona-dev] Shared Bug View|
I think the next logical step would be to allow a Team Members to create Shared Resource Lists. The Shared Resource List would contain the Resource URI and the Resource Type URI.
We need to create a registry to map Resource Types to Resource Editors. We could then use the Resource Type URI in the Shared Resource List launch the correct Resource Editor and specify the Resource URI from the Shared Resource List.
I think we could then share lists of any resources with an available resource editor…
Why don’t we enter it as an enhancement bug and leave it until later. Do want to enter it or should I?
It would be better if the bug could be clicked on from the chat text, and a browse window shows up with the bug.
While the chat display window is not a browser window. I think the code does support the linking from chat text.
I will look at this
I will also look at making the chat window a browser window
As we were using Chat in
Each person in Team in a Context can create list of bugs they want to talk about because they are fixed or have a problem
During Chat when a person decides it is time to discuss their bug list, he then clicks on the Share Bug List button. (I don’t know where this button goes.)
All active participants in the chat room have their Bugzilla View updated with the Shared Bug List.
Then it is easy to tab between chat and the bug view.
Just an idea. - Glenn Everitt
You can enter a comma separated list of bug numbers in Actions text entry box and click find to get a specific list:
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.