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

Bug 218476

Summary:	[workflow] update Trac task with revision id upon commit of changeset
Product:	z_Archived	Reporter:	Alex Batlin <Alex.Batlin>
Component:	Mylyn	Assignee:	Project Inbox <mylyn-triaged>
Status:	CLOSED MOVED	QA Contact:
Severity:	enhancement
Priority:	P4	CC:	hazen, jim.kass
Version:	3.6	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:
Bug Depends on:	306790
Bug Blocks:	357472

Description Alex Batlin

2008-02-11 04:54:35 EST

Build ID: 3.3

Steps To Reproduce:
1. Use Subclipse and Trac plugins for Mylyn
2. Create a new Trac task and start making changes, to build up the change set
3. Commit change set, with auto created comment.
4. Trac ticket is not updated (in comment or elsewhere) to indicate that a related to task commit has occured.


More information:
I am currently using Trac's post-commit hook to scan for svn ci comments, and add the changeset rev id to a comment field in the trac ticket. This works, but seems convoluted. Is it possible for Mylyn to update the change set related task with changeset id as part of the commit operation i.e. do not just do a svn ci, but also update the trac ticket.

Comment 1 Steffen Pingel

2008-02-11 14:07:52 EST

Just to clarify: Does the Trac task get an incoming indicator for the comment added by the commit hook when it is synchronized or opened?

Comment 2 Alex Batlin

2008-02-12 04:15:42 EST

(In reply to comment #1)
> Just to clarify: Does the Trac task get an incoming indicator for the comment
> added by the commit hook when it is synchronized or opened?

Yes it does. What I am not clear about though, is whether or not the hook should be required at all i.e.

a. is it intentional that Mylyn Trac plugin does not update the task tickets with changeset

or 

b. it should do so, but does not

If it's (b) then it is a bug. If it's (a), then I will kindly ask for enhancement to be added to update trac task. This is very useful, as when viewing the ticket in Trac, if it has a the changeset #NNN in comment, I can very quickly see the associated set of changes with the task. 

Current implementation does not do that, so I can browse the code in Trac and see the related task, but not the changeset from the task. As mentioned, I can workaround this by having the post-commit hook, but it's seems clumsy as seems the best solution is for Mylyn to inact the commit, and at the same time update the task, so no need for the hook.

Comment 3 Steffen Pingel

2008-02-12 16:18:44 EST

Thanks for the explanations. It is (a) - a feature that is currently not supported by Mylyn. I have marked the report as helpwanted to indicate that adding this feature is currently not a high priority but we would be happy to support and accept a contribution.

Comment 4 Alex Batlin

2008-02-13 04:44:45 EST

(In reply to comment #3)
> Thanks for the explanations. It is (a) - a feature that is currently not
> supported by Mylyn. I have marked the report as helpwanted to indicate that
> adding this feature is currently not a high priority but we would be happy to
> support and accept a contribution.

great, many thanks. that clears up my understanding. if I have some spare time, I will check to see if I can contribute something.

Comment 5 Steffen Pingel

2010-05-06 04:31:03 EDT

*** Bug 311812 has been marked as a duplicate of this bug. ***

Comment 6 Andy Schlaikjer

2011-05-19 11:50:47 EDT

I found this issue while searching for solutions which would allow Trac task status modification based on commit message:

I'd like to be able edit the Mylyn auto-generated commit message, e.g. from

"NEW - # 123: Issue title..." to
"FIXED - # 123: Issue title..."

to allow automatic linking of changeset with task as well as update of task status from NEW to FIXED.

For the time being, a subversion post-commit hook sounds like the right approach.

Comment 7 Eclipse Webmaster

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