Bugzilla – Full Text Bug Listing
| Summary: | allow local tasks to be promoted to repository tasks | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Mik Kersten <mik.kersten> | ||||||||
| Component: | Mylyn | Assignee: | Mik Kersten <mik.kersten> | ||||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||||
| Severity: | enhancement | ||||||||||
| Priority: | P3 | CC: | david_syer, eclipse, ekuleshov, gerry.spm+eclipsebug, mjmeijer, nhapke, robert.elves, wmitsuda | ||||||||
| Version: | unspecified | ||||||||||
| Target Milestone: | 3.0 | ||||||||||
| Hardware: | PC | ||||||||||
| OS: | All | ||||||||||
| Whiteboard: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Mik Kersten
Good stuff. It should be helpful when you work on some feature, and only later you decide to submit the patch, creating the bug report. I only think it shouldn't force you to create a bug report using mylar to be able to "transfer" the context information between tasks. I should be able to create the task using the web/other client and then associate it with the local task. I know what you mean. Note that we have copying and pasting of task contexts as an orthogonal enhancement: bug 126237 BTW, with alternative synchronization proposal this may not be an issue and would allow to have the same task in more then one repository (i.e. company private and public). Great suggestion Robert. This would be so useful for me atm... if only. *** Bug 197774 has been marked as a duplicate of this bug. *** There continues to be interest in this feature. I would also like the ability to convert a repository task to another repository task. This would be useful when a bug is filed against something like Mylyn's Bugzilla connector, but it turns out to be a Bugzilla bug and it should be submitted to them. The more general approach for this would be to allow a user to convert any task to any other task (local -> repository, repository->local and repository->repository). This functionality could be support through Operations -> Clone Task. The menu is currently disabled for local tasks but it should be fairly straight forward to implement that. Thoughts? +1 Nice and simply approach to supporting this. If it's as quick a fix as that we could consider for 2.3. Maarten, would you be interested in providing a patch? (In reply to comment #10) > Maarten, would you be interested in providing a patch? > I'm currently on a rather busy project, but will look into it to see whether the Clone Task can be generalized to handle local tasks as well. What is the 2.3 time frame? (In reply to comment #11) > (In reply to comment #10) > > Maarten, would you be interested in providing a patch? > > > I'm currently on a rather busy project, but will look into it to see whether the > Clone Task can be generalized to handle local tasks as well. What is the 2.3 > time frame? Maarten, if you don't have the time to do this before 2.3 I can look at this. When we remove the suppress showing for local tasks see comment 19 in bug 161646: support for Clone this bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=161646#c19 put in by Mik the action is enabled for all task types. TaskUiUtil.openNewTaskEditor() allows choosing local as well. The net effect is that this bug is resolved by taking away limitations in plugin.xml. Created attachment 87669 [details]
plugin.xml patch
Remove disable for Local Tasks
Created attachment 87670 [details]
mylyn/context/zip
(In reply to comment #11) > I'm currently on a rather busy project, but will look into it to see whether the > Clone Task can be generalized to handle local tasks as well. What is the 2.3 > time frame? No problem Maarten. This bug is not high priority. There are still more than four weeks of time until the Mylyn 2.3 release on Feb. 27. I think the patch will need some additional work. When I tried to clone a local task the priority, description and URL were not cloned to the new task. It would also be valuable to have a test case that verifies that properties of local tasks are cloned correctly. Maarten, let me know if you want to look at that. Frank, thanks for the offer to help out. In case we don't get this resolved I'll hand it over to you :). I took that out because we were not properly formatting the clone of local tasks. Will take a quick look now. I made clone work properly for local tasks by properly handling missing key/IDs and adding the Notes to the description. Thanks for patch removing the restriction Maarten, I applied it. There could be additional feature requests for this functionality, as per my listing in the description. But the core features are there now, the rest can be done manual, and we can take additional requests for automation. Created attachment 87684 [details]
mylyn/context/zip
(In reply to comment #18) > I made clone work properly for local tasks by properly handling missing key/IDs > and adding the Notes to the description. Thanks for patch removing the > restriction Maarten, I applied it. You're welcome, too small to add to my total on http://www.eclipse.org/mylyn/contributors/ I presume ;-) (In reply to comment #18) > I made clone work properly for local tasks by properly handling missing key/IDs > and adding the Notes to the description. Thanks for patch removing the > restriction Maarten, I applied it. I was still thinking about how to make LocalTask behave exactly like a RepositoryTask so that special casing is not necessary. Is that still an interesting option for 3.0? (In reply to comment #20) > You're welcome, too small to add to my total on > http://www.eclipse.org/mylyn/contributors/ I presume ;-) Yes, too small this time around because this required a bunch of other work. But consider my owing you one ;) Also note that I updated the stats today and yours are climbing :) http://www.eclipse.org/mylyn/contributors/ Also note my comment on bug 214525. |