Bugzilla – Full Text Bug Listing
| Summary: | improve save lifecycle for new local tasks | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Eugene Kuleshov <ekuleshov> | ||||||
| Component: | Mylyn | Assignee: | Steffen Pingel <steffen.pingel> | ||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||
| Severity: | enhancement | ||||||||
| Priority: | P3 | CC: | mik.kersten, rolf, steffen.pingel | ||||||
| Version: | unspecified | ||||||||
| Target Milestone: | 3.1 | ||||||||
| Hardware: | PC | ||||||||
| OS: | Windows All | ||||||||
| Whiteboard: | |||||||||
| Attachments: |
|
||||||||
|
Description
Eugene Kuleshov
Bugzilla versions of 0.5 and dev added. Rob, supporting this mode, which I agree is better, will require us to be able to edit tasks that have not yet been edited to the list. It is related to the common editor and to bug 131038. What is the status/progress of this issue? This depends on comment#7 on bug# 138145. Do we want to have a new editor opening or should the task just be created in place in the tasklist with the current rename action? What are your thoughts on this Eugene? Mik? (In reply to comment #3) > This depends on comment#7 on bug# 138145. Do we want to have a new editor > opening or should the task just be created in place in the tasklist with the > current rename action? What are your thoughts on this Eugene? Mik? I was orignally leaning towards opening editor, but after looking at Jazz's planning editor it seems to me that not opening editor for local tasks is probably better idea. Though they should not be added to the task list if user hit escape even after entering some text. BTW, it would be interesting feature to be able to promote/convert local tasks to repository. So now that local tasks no loger bring up the editor can we mark this 'worksforme'? Rob removing opening after creation and it was too confusing, especially when creating tasks via the File -> New menu. Also, it is consistent with file creation, but that alone is not a good enough reason to keep it. So let's reconsider this decision at some point and leave it open for now. We also need to consider Eugene's suggestion of not 'saving' the task until it has first been saved, but that may mean complicating things by allowing the task list to show unsaved tasks. Ability to promote is something I've wanted for a long time, created bug 152211 Ooops, didn't mean to close this yet. To date we've taken an alternate approach (with repository tasks) of giving the user an X to delete the new task. Once local task editor is merged with the repository task editor, Steffen, do you see the interaction being what it currently is for repository tasks (i.e. task will get created but will have a perpetual X)? Or do with go with the more traditional creation upon first save? The X has been working well for me for unsubmitted repository tasks so I am +1 to also use it for local tasks. It would also make it consistent with unsubmitted tasks. +1 *** Bug 227126 has been marked as a duplicate of this bug. *** Created attachment 114864 [details]
screenshot
The delete button has been added to the local task editor (see attachment or bootstrap). Created attachment 114865 [details]
mylyn/context/zip
|