Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 167351

Summary: Permit auto-sync of repository tasks when commits made against them.
Product: z_Archived Reporter: Ian Whalley <inw-eclipse>
Component: MylynAssignee: Project Inbox <mylyn-triaged>
Status: CLOSED MOVED QA Contact:
Severity: enhancement    
Priority: P4 Keywords: helpwanted
Version: 0.9   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Ian Whalley CLA 2006-12-10 13:58:11 EST 
Eclipse Build ID: M20060921-0945
Mylar version: 0.9.2.2

Steps To Reproduce:
1. Find a repository that has comments added to the bug when commits are made against the bug (e.g. Bugzilla with SCMbug)
2. Make commits against tasks from that repository.
3. Observe that you must manually refresh the task after committing.

Our installation of SCMbug forces committers to specify a valid bug number when committing changes to the source, and then it automatically mirrors the SVN commit message into a comment on the bug.  It would be nice if Mylar had a setting wherein it would auto-sync the task when commits are made against that task -- currently, this must be done by hand to avoid clashes later.
Comment 1 Eugene Kuleshov CLA 2006-12-10 14:29:32 EST 
I wonder if any other issue tracking system does that?

By the way, at some point I was suggesting to add feature to synchronize other way around. If issue tracking system received new comment, or even context attachment, then we know what projects has been changed, so only these projects need to be synchronized. Though I am not sure if there is an unified Team API for kicking synchronizations.
Comment 2 Ian Whalley CLA 2006-12-10 14:33:44 EST 
 (In reply to comment #1)
Perhaps my report was confusingly worded.  I was not suggesting that we synchronise the project following a commit from someone else, but instead that we synchronise the task following a commit by me.
Comment 3 Eugene Kuleshov CLA 2006-12-10 14:58:32 EST 
It was clear enough to me. However, personally I don't see much need to rush task synchronization for changes you already know about. Also, why synchronize only tasks you committed but not tasks you got in the incoming changes?

My comment was referring to separate but somehow related issue, when synchronizing many projects with version control is quite slow. That is why I reminded about that old idea for the opposite synchronization.
Comment 4 Ian Whalley CLA 2006-12-10 15:04:32 EST 
 (In reply to comment #3)
> It was clear enough to me. However, personally I don't see much need to rush
> task synchronization for changes you already know about. 

True, but it might be nice :-- hence my setting the priority to ENHANCEMENT :).
Comment 5 Eugene Kuleshov CLA 2006-12-10 16:20:52 EST 
By the way, if we get into implementing this, it seem like a good idea to enable 3rd party plugins to add arbitrary attributes to the task repositories, then contribute own pages for editing these attributes (e.g. force task sync after commit) and also somehow notify those guys about commits and other activities. Then we'll have flexible infrastructure for implementing this kind of stuff.
Comment 6 Mik Kersten CLA 2007-03-22 14:42:55 EDT 
Out of scope for 2.0 so marking helpwanted in case anyone is interested in contributing this.
Comment 7 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