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

Bug 359441

Summary:	Commit comment does not get updated upon change of active task
Product:	z_Archived	Reporter:	Sébastien Gandon <sgandon>
Component:	Mylyn	Assignee:	Mylyn Inbox <mylyn-inbox>
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	Macintosh
OS:	Mac OS X - Carbon (unsup.)
Whiteboard:

Description Sébastien Gandon

2011-09-29 11:33:46 EDT

Build Identifier: 

hello,
When I try to commit a change the commit template the active task, then I cancel it.
If I switch the active task to another task, and try to commit the same code I have the commit comment of the previous task and not the newly selected task.
see Atlassian discussion : https://answers.atlassian.com/questions/6604/eclipse-svn-commit-comments-do-not-reflect-the-jira-active-issue-in-mylyn

Reproducible: Always

Steps to Reproduce:
It is easy to reproduce,

select one active task (Task 1).
change one file
open the svn commit window
check Task 1 is correctly mentionned in the commit comments (do not commit, cancel)
activate another task (Task 2)
open the svn commit window
Task 1 is still rmentionned not Task 2 as expected.
I have tried with the 2 plugins for SVN that is Subversive and Subclipse with the same behaviour in the end.

here are the versions of the feature I have installed.

com.atlassian.connector.commons (3.0.1.v20110812) "Atlassian Connector for Eclipse Branding"

com.atlassian.connector.eclipse (3.0.1.v20110812) "Atlassian Connector for Eclipse Branding"

com.atlassian.connector.eclipse.bamboo (3.0.1.v20110812) "Atlassian Connector for Eclipse Branding"

com.atlassian.connector.eclipse.commons (3.0.1.v20110812) "Atlassian Connector for Eclipse Branding"

com.atlassian.connector.eclipse.crucible (3.0.1.v20110812) "Atlassian Connector for Eclipse Branding"

com.atlassian.connector.eclipse.jira (3.0.1.v20110812) "Atlassian Connector for Eclipse Branding"

com.atlassian.connector.eclipse.monitor (3.0.1.v20110812) "Atlassian Connector for Eclipse Branding"

com.collabnet.subversion.merge.feature (2.2.4) "CollabNet Subversion Merge Client"

.....

org.eclipse.mylyn_feature (3.6.0.v20110608-1400) "Mylyn"

org.eclipse.mylyn.bugzilla_feature (3.6.0.v20110608-1400) "Mylyn"

org.eclipse.mylyn.context_feature (3.6.0.v20110608-1400) "Mylyn"

org.eclipse.mylyn.ide_feature (3.6.0.v20110608-1400) "Mylyn"

org.eclipse.mylyn.java_feature (3.6.0.v20110608-1400) "Mylyn"

org.eclipse.mylyn.pde_feature (3.6.0.v20110608-1400) "Mylyn"

org.eclipse.mylyn.team_feature (3.6.0.v20110608-1400) "Mylyn"

org.eclipse.mylyn.wikitext_feature (1.5.0.v20110608-1400) "Mylyn"

...

org.tigris.subversion.clientadapter.feature (1.6.12) "Subversion Client Adapter"

org.tigris.subversion.clientadapter.javahl.feature (1.6.17) "Subversion JavaHL"

org.tigris.subversion.subclipse (1.6.18) "SVN Team Provider Core"

org.tigris.subversion.subclipse.graph.feature (1.0.9) "Subversion Revision Graph"

org.tigris.subversion.subclipse.mylyn (3.0.0) "Subclipse Integration for Mylyn 3.x"

Comment 1 Sébastien Gandon

2011-09-29 11:34:28 EDT

I forgot to mention, this happens with Subversive , Subclipse and apparently Bugzilla as well.

Comment 2 Steffen Pingel

2011-11-05 14:56:13 EDT

That is the intended behavior. If you change files they get automatically assigned to a change set related to the active task. The change set will still reflect the old task even if you commit files later. This allows you to work on multiple tasks and still maintain the proper change set association.

If you intend to commit files under a different task you have to move them to the corresponding change set in the Synchronize view prior to committing.