Bug 195738 - Context import dialog should provide an ability to create a local task for this context
Summary: Context import dialog should provide an ability to create a local task for th...
Status: CLOSED MOVED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: unspecified   Edit
Hardware: PC All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2007-07-07 07:13 EDT by Jevgeni Holodkov CLA
Modified: 2010-03-25 16:14 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jevgeni Holodkov CLA 2007-07-07 07:13:36 EDT
If I am importing a context and I don't have a task for it, I don't want to quit the dialog, create the task and then go back to the dialog, I want to do create this task right in the Task Context Import Dialog. This is especially important if the context received synchronously using ECF, since exiting the dialog will stop context sharing and the sender will need to initiate context sharing again.
Comment 1 Eugene Kuleshov CLA 2007-07-07 11:16:05 EDT
That would be quite useful. However I think that exported context archive should also have all the details about corresponding task, such as AbstractTask (in the same form as connector's externalizer externalize it) and RepositoryTaskData (in the same form as it is externalized for the offline storage). The latter one actually should be enough to open repository editor for previewing the task. 

An alternative to this could be to send task url along with the context, but that won't work for local tasks and tasks that came from repository user don't have in his workspace. Which probably mean that context externalizer should also include repository info along with context data.
Comment 2 Mik Kersten CLA 2007-10-18 18:19:07 EDT
Eugene: agreed on all but RepositoryTaskData, which I think we should hold off on for now because it is considered cached data that may be best to retrieve live, although I do see use cases where this could be relevant.  But I think that you are referring to the case of transferring a task+context, and Jevgeni is only talking about transferring context.

Jevgeni: my sense is that if the sender chose to transfer context only, then the recipient will already have a task that they will want to put this context on.  So what if this instead invokes the same dialog as "Context -> Copy to..." (see Task List popup menu)?
Comment 3 Eugene Kuleshov CLA 2007-10-18 20:48:32 EDT
(In reply to comment #2)
> ... because it is considered cached data that may be best to retrieve live

Not necessarily. Recipient may not have access (no permissions or even host could not be visible).

You actually have a good point about having task. It seems like IM conversation should verify if task is actually available to the recipient before sending context.

BTW, even for "Context / Copy to..." action it would be useful to have "New Task" action. Created bug 206840
Comment 4 Mik Kersten CLA 2007-11-23 14:12:08 EST
Jevgeni: reassign to Inbox.  If you would like to work on this further just let us know.
Comment 5 Eclipse Webmaster CLA 2022-11-15 11:45:08 EST
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