Community
Participate
Working Groups
The last page where all the details about issue filled in should be done as an editor. So, wizard would just allo to choose repository and product and then open new editor with all task details.
Yup, this would address the problem of being stuck in a modal dialog when you need additional info from your workspace in order to populate the report.
It reminds me that personal task should work the same. Open an editor immediately without creating task. Create task on save and if closed without saving just discard task. All url fetch would come handy right in the editor as well...
Yes, Rob, let's just get rid of that dialog for the personal tasks. It was a work-around for when we didn't have a good editor to open automatically. Please note that the form title should update when the Description changes.
Mik, Robert, any chance to resolve this any time soon?
We'll do this as a part of the common task editor.
(In reply to comment #5) > We'll do this as a part of the common task editor. Dammit! Another two months. :-(
I doubt it will take that long. The common edtior is high priority, but it will take quite a bit of work because it will require common offline storage.
*** Bug 106922 has been marked as a duplicate of this bug. ***
Rob, now that we'll (hopefully) be able to get rid of NewBugReport let's try to get this in to 0.5.3.
Doesn't look like it made to 0.5.3.
Unfortunately not but it is scheduled for this week! :)
*** Bug 146823 has been marked as a duplicate of this bug. ***
I'm liking the looks of things so far. Haven't committed anything yet but it all works well! I just would like to make the new bug editor saveable and have the reports not submitted yet open upon workbench startup. Does that sound like the right behaviour?
Yes, as long as it's not too much work ;)
For now I've forced the new bug editor to always be dirty (saving does nothing).
Created attachment 44711 [details] mylar/context/zip new bug editor and wizards
Fixed - New bug reports are now filled out in an editor.
Does it mean that it is not possible to create new issues when offline? I also noticed that "Finish" in wizard takes some time (probably on first call) before editor appear.
Actually, at the moment it is possible if you have previously been online and the repository configuration has been cached, otherwise you'll see an error presented in the wizard when you press Finish. Yes, the first call to finish may take a bit longer than usual if it needs to retrieve the repository configuration from the server. The next time should be instant since it is cached. :)
(In reply to comment #19) > Actually, at the moment it is possible if you have previously been online and > the repository configuration has been cached, otherwise you'll see an error > presented in the wizard when you press Finish. I presume "cached" information is not survive Eclipse restart? > Yes, the first call to finish may take a bit longer than usual if it needs to > retrieve the repository configuration from the server. The next time should be > instant since it is cached. :) Don't you think it worth to make it asyncronous?
> I presume "cached" information is not survive Eclipse restart? Actually now the repository configuration is cached to disk so configuration data now survives workbench restart. > Don't you think it worth to make it asyncronous? The reason for this is that the configuration data is needed to populate the attribute options in the editor. Without the configuration we can't really present a complete new bug editor. But since that information is cached it will only lag the one time per repository.
