Bugzilla – Full Text Bug Listing
| Summary: | [workflow] option to always attach context | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Mark Addleman <mark_addleman> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | Michael.Valenta |
| Version: | unspecified | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
| Bug Depends on: | 109552 | ||
| Bug Blocks: | 357472 | ||
|
Description
Mark Addleman
Do you mean that you would like the commit action to invoke a submission to the task repository (e.g. Bugzilla)? We've been brainstorming this and were wondering if it would make more sense to add a "Commit Changes" checkbox next to the "Attach Context" checkbox on the task editor. I like the idea of using the task editor as the main mechanism to commit back to CVS (or whatever). As a convenience, I think there should be an option on the task pop-up menu (from the Task List view) to also attach the context and commit. The one fly in that ointment is that I (and many others, I bet) sometimes forget to activate a Mylyn task before I begin working on a task. That means that some files can end up outside the Mylyn context and outside the change set. I don't need the saved context to be entirely accurate, but I definitely need the committed change set to be accurate. Therefore, if I use Mylyn as my primary means to commit files, I would need some way of verifying the context and change set before the commit occurs. An alternative would be to provide a mode where no files can be edited without a Mylyn task being active. In certain development phases, I think that can be very useful but it touches on larger issues of development team policies and enforcement. Excellent points. The middle paragraph in your comment is exactly why we removed the "Commit Context" action from the Task List popup menu and encourage use of the Synchronize view, where you can manaully add missed files to your change set. I wonder if we can embedd some kind of filtered Synchronize view right into the Task Editor... Maybe Mylyn could contribute a new commit model. The model would be very similar to the Change Set model, but also allow the option to save the context to the task repository. I believe that would require very little UI change and the user wouldn't need to learn new commit behaviors. Mylyn is currently using automatically managed "Change Sets" model. Not sure if custom model would really allow to invoke additional actions post commit. Maybe Michael could give us some clue. Also note that not all VCS provides support models. I only saw that for Team/CVS provider. There is no Commit participation facility for CVS but thre have been requests (bug 170305 and bug 78133 among others). Let's consider this for 3.1. Please vote if interested. However, as per comment#7 we still don't have a good hook. Marking as helpwanted since there is currently no clear implementation strategy. 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 |