Community
Participate
Working Groups
"Context / Copy to..." action should allow to create new task right from the dialog used to select task.
Makes sense to me. Seems like a "New Task..." button at the bottom of the dialog would suffice.
(In reply to comment #1) > Makes sense to me. Seems like a "New Task..." button at the bottom of the > dialog would suffice. I start with this but if I create the new Button and run the NewTaskAction from widgetSelected i got the following problem. After the "Net Task" Dialog finished the newly created TaskEditor is behind the opend Dialog. So it is not possible to fill the neede Fileds and save the new Task. How should we make up the UI so that the new Task is enterd before we come back to the TaskSelectionDialog.
Frank, it would make sense close "Open Dialog" when "new task" action is invoked and pass context to the new task editor. So, when context is passed, context for the new task can be populated upon editor completion and no new UI will be needed.
(In reply to comment #3) > Frank, it would make sense close "Open Dialog" when "new task" action is invoked > and pass context to the new task editor. So, when context is passed, context for > the new task can be populated upon editor completion and no new UI will be > needed. OK I can do this but if I see it right the problem is that the new API (TaskSelection) can used to save the context until the TaskEditor is opened. But for save the Context I need the ID of the new Task. This is set with the save button. How to solve this problem.
Frank, I think AbstractRepositoryTaskEditor.submitToRepository() can be updated to call something like the following after submission job is completed: ContextCorePlugin.getContextManager().cloneContext( sourceTask.getHandleIdentifier(), targetTask.getHandleIdentifier()); you'll need to save the source task (probably in the editor instance) when new task editor is created.
Created attachment 83374 [details] mylyn/context/zip
Created attachment 83586 [details] patch To get this work I put a new field in TaskSelection and NewTaskEditorInput to pass the Information from the Action to the Editor.
Created attachment 83587 [details] mylyn/context/zip
Rob: please queue for review.
Frank, can you explain why the context is cloned in the task editor and not in NewBugzillaTaskWizard?
(In reply to comment #10) > Frank, can you explain why the context is cloned in the task editor and not in > NewBugzillaTaskWizard? Steffen, currently im at work, so I did not have the code in front of my, but if I remember it right the problem was. In NewBugzillaTaskWizard you get an new task but the ID is not set correctly. The Id get set during the action behind the submit button in task editor. I will verify this at home.
Yes, that definitely makes it more difficult to implement this feature and passing the context in the editor input might indeed be the best way to do it. The underlying problem is that the actual task is created with a different id when it is submitted to the repository. For 3.0 the framework should support storing contexts for unsubmitted tasks and migrate the context when the actual task is created (related to bug 152272).
Need to defer: http://wiki.eclipse.org/index.php/Mylyn/3.0_Plan#Deferred_Items
Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn
