Toad World® Forums

Check in Associations not working with Team foundation Server 2013


#1

Build version 12.5.0.84.

Defect number 114398 was confirmed as being fixed as part of this build, however, despite the fact I can now see all valid work items assigned to me, there is still a problem when selecting an item from the list (or typing the work item/bug number manually) in that no association is made between the change set being checked-in and the bug/work item. Toad build 12.5.0.84 and Team Foundation Server 2013 with update 2 version number 12.0.30324.0

Steps to re-create:

  • in TFS assign a product backlog item or bug to yourself.

  • in toad check out a given package/proc under source control with TFS.

  • change/add a comment to the file.

  • select check in from the action menu, and switch to the “Work Items” tab as shown in the below screen print.

  • select the work item you assigned to yourself earlier, and check the “Selected” checkbox.

  • click ok.

-go back into TFS 2013 and bring up your work item/bug. Note that there is no “Link” to the change set just checked in, see screen print 2 below.


#2

I am trying to recreate this. Thank you for the clear reproduction steps.

From: bryan.macmillan [mailto:bounce-bryanmacmillan@toadworld.com]

Sent: Tuesday, May 13, 2014 7:42 AM

To: toadoraclebeta@toadworld.com

Subject: [Toad for Oracle - Beta Discussion Forum] Check in Associations not working with Team foundation Server 2013

Check in Associations not working with Team foundation Server 2013

Thread created by bryan.macmillan

Build version 12.5.0.84.

Defect number 114398 was confirmed as being fixed as part of this build, however, despite the fact I can now see all valid work items assigned to me, there is still a problem when selecting
an item from the list (or typing the work item/bug number manually) in that no association is made between the change set being checked-in and the bug/work item. Toad build 12.5.0.84 and Team Foundation Server 2013 with update 2 version number 12.0.30324.0

Steps to re-create:

  • in TFS assign a product backlog item or bug to yourself.

  • in toad check out a given package/proc under source control with TFS.

  • change/add a comment to the file.

  • select check in from the action menu, and switch to the “Work Items” tab as shown in the below screen print.

  • select the work item you assigned to yourself earlier, and check the “Selected” checkbox.

  • click ok.

-go back into TFS 2013 and bring up your work item/bug. Note that there is no “Link” to the change set just checked in, see screen print 2 below.

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - Beta
notifications altogether.

Toad for Oracle - Beta Discussion Forum

Flag
this post as spam/abuse.


#3

Hello,

I am using Visual Studio 2013 Professional on the client and TFS 2013. I am able to recreate this when there is no modification to the object code. If I make
a change to the object source and check in, it appears to work correctly. My test is as follows:

Check out from Team Coding Viewer in the Dashboard

Double click to open in the editor. Make a change to the comments. Compile.

Check in. Check one or more Work items in the work item tab.

You should get a message like this in the output window. “Changeset 191 linked to Work Item 7”

If no modification is made to the object TFS 2013 does not allow Toad to force a revision, and I get an error message in the output window saying that the work
item link failed. I think this is also the case with TFS 2012 , but not TFS 2010.

Are you seeing this behavior?

Stephen

From: bryan.macmillan [mailto:bounce-bryanmacmillan@toadworld.com]

Sent: Tuesday, May 13, 2014 7:42 AM

To: toadoraclebeta@toadworld.com

Subject: [Toad for Oracle - Beta Discussion Forum] Check in Associations not working with Team foundation Server 2013

Check in Associations not working with Team foundation Server 2013

Thread created by bryan.macmillan

Build version 12.5.0.84.

Defect number 114398 was confirmed as being fixed as part of this build, however, despite the fact I can now see all valid work items assigned to me, there is still a problem when selecting
an item from the list (or typing the work item/bug number manually) in that no association is made between the change set being checked-in and the bug/work item. Toad build 12.5.0.84 and Team Foundation Server 2013 with update 2 version number 12.0.30324.0

Steps to re-create:

  • in TFS assign a product backlog item or bug to yourself.

  • in toad check out a given package/proc under source control with TFS.

  • change/add a comment to the file.

  • select check in from the action menu, and switch to the “Work Items” tab as shown in the below screen print.

  • select the work item you assigned to yourself earlier, and check the “Selected” checkbox.

  • click ok.

-go back into TFS 2013 and bring up your work item/bug. Note that there is no “Link” to the change set just checked in, see screen print 2 below.

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - Beta
notifications altogether.

Toad for Oracle - Beta Discussion Forum

Flag
this post as spam/abuse.


#4

Hi Stephen,

On further investigation, it would appear the problem I have reported above is a consequence of another issue and not the root cause.

When I am checking the object out using Team Coding Viewer I am being prompted in 12.5 to “Select a Project”, I am not getting the same prompt in 12.1. The problem in 12.5, it would appear, is that I can only drill down 2 levels from the root of the custom collection. On doing so toad is updating the “Code Collections” for these objects, which means when I come to check the object back in the following message appears in the “Output” window. " Error: Error selecting project in Microsoft Team Foundation Server (Custom Collection)"

My Config:

toad 12.5.0.84 x64 version

Team Coding is set up to use the external command-line client pointing at Visual Studio 2013 Ultimate, with TFS 2013 with a working directory mapped. Team coding is also set to “Use Custom Collection” as my company name, and a virtual directory as “/tfs”

Steps to reproduce:

  • in VS/TFS map a working directory to “C:_TFS\Source” where the $/ of your custom collection should map to.

  • In TFS under “MyTeam” add a folder called “Oracle”, under which add your DB Schema to be version. Under which should map Fnc, Pkf, Pks etc.

  • In toad 12.1 select “Team Coding Dashboard” and switch to “Code Collections” change the schema_pks “VCS Project” by double clicking on it. Click the “…” button next to VSC Project in the popup. Note in 12.1 you can drill down 4 levels to get to your Pks directory under your schema.

  • Repeat the last step in 12.5, now note when you receive the “Select Project” dialog, that you are unable to drill down more than 2 directory levels.

The last item above means that your VCS project and TFS become out of sync, resulting in the initial problem reported above.

If you require a VCS output log, or we can set up a go-to meeting to reproduce further?


#5

Brian,

The internal client and external client use a different code base, do you get the same behavior using the internal client?

Stephen

From: bryan.macmillan [mailto:bounce-bryanmacmillan@toadworld.com]

Sent: Tuesday, May 13, 2014 1:17 PM

To: toadoraclebeta@toadworld.com

Subject: RE: [Toad for Oracle - Beta Discussion Forum] Check in Associations not working with Team foundation Server 2013

RE: Check in Associations not working with Team foundation Server 2013

Reply by bryan.macmillan

Hi Stephen,

On further investigation, it would appear the problem I have reported above is a consequence of another issue and not the root cause.

When I am checking the object out using Team Coding Viewer I am being prompted in 12.5 to “Select a Project”, I am not getting the same prompt in 12.1. The problem in 12.5, it would appear,
is that I can only drill down 2 levels from the root of the custom collection. On doing so toad is updating the “Code Collections” for these objects, which means when I come to check the object back in the following message appears in the “Output” window.
" Error: Error selecting project in Microsoft Team Foundation Server (Custom Collection)"

My Config:

toad 12.5.0.84 x64 version

Team Coding is set up to use the external command-line client pointing at Visual Studio 2013 Ultimate, with TFS 2013 with a working directory mapped. Team coding is also set to “Use Custom Collection”
as my company name, and a virtual directory as “/tfs”

Steps to reproduce:

  • in VS/TFS map a working directory to “C:_TFS\Source” where the $/ of your custom collection should map to.

  • In TFS under “MyTeam” add a folder called “Oracle”, under which add your DB Schema to be version. Under which should map Fnc, Pkf, Pks etc.

  • In toad 12.1 select “Team Coding Dashboard” and switch to “Code Collections” change the schema_pks “VCS Project” by double clicking on it. Click the “…” button next to VSC Project in the
    popup. Note in 12.1 you can drill down 4 levels to get to your Pks directory under your schema.

  • Repeat the last step in 12.5, now note when you receive the “Select Project” dialog, that you are unable to drill down more than 2 directory levels.

The last item above means that your VCS project and TFS become out of sync, resulting in the initial problem reported above.

If you require a VCS output log, or we can set up a go-to meeting to reproduce further?

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - Beta
notifications altogether.

Toad for Oracle - Beta Discussion Forum

Flag
this post as spam/abuse.


#6

Brian,

Can you also send me the VCS Output log?

Thanks

Stephen

From: bryan.macmillan [mailto:bounce-bryanmacmillan@toadworld.com]

Sent: Tuesday, May 13, 2014 1:17 PM

To: toadoraclebeta@toadworld.com

Subject: RE: [Toad for Oracle - Beta Discussion Forum] Check in Associations not working with Team foundation Server 2013

RE: Check in Associations not working with Team foundation Server 2013

Reply by bryan.macmillan

Hi Stephen,

On further investigation, it would appear the problem I have reported above is a consequence of another issue and not the root cause.

When I am checking the object out using Team Coding Viewer I am being prompted in 12.5 to “Select a Project”, I am not getting the same prompt in 12.1. The problem in 12.5, it would appear,
is that I can only drill down 2 levels from the root of the custom collection. On doing so toad is updating the “Code Collections” for these objects, which means when I come to check the object back in the following message appears in the “Output” window.
" Error: Error selecting project in Microsoft Team Foundation Server (Custom Collection)"

My Config:

toad 12.5.0.84 x64 version

Team Coding is set up to use the external command-line client pointing at Visual Studio 2013 Ultimate, with TFS 2013 with a working directory mapped. Team coding is also set to “Use Custom Collection”
as my company name, and a virtual directory as “/tfs”

Steps to reproduce:

  • in VS/TFS map a working directory to “C:_TFS\Source” where the $/ of your custom collection should map to.

  • In TFS under “MyTeam” add a folder called “Oracle”, under which add your DB Schema to be version. Under which should map Fnc, Pkf, Pks etc.

  • In toad 12.1 select “Team Coding Dashboard” and switch to “Code Collections” change the schema_pks “VCS Project” by double clicking on it. Click the “…” button next to VSC Project in the
    popup. Note in 12.1 you can drill down 4 levels to get to your Pks directory under your schema.

  • Repeat the last step in 12.5, now note when you receive the “Select Project” dialog, that you are unable to drill down more than 2 directory levels.

The last item above means that your VCS project and TFS become out of sync, resulting in the initial problem reported above.

If you require a VCS output log, or we can set up a go-to meeting to reproduce further?

To reply, please reply-all to this email.

Stop receiving emails on this subject.

Or
Unsubscribe from Toad for Oracle - Beta
notifications altogether.

Toad for Oracle - Beta Discussion Forum

Flag
this post as spam/abuse.


#7

Hi Stephen,

After switching to the Internal Client, I can confirm the issues with multi nested folders in TFS is back to being functional again and I can check items back into TFS, and also associate work items successfully**. Hence it would appear the issue is with the external command line client. Historically we have used the external client as older versions of toad supported more features in the external client than internal.


**One point I have noted about the work item check in association is that the work item association seems to be happening after the check-in and not at the same time/part of the check in, hence toad will override any check in policies in force.

To demonstrate this, go into Visual Studio -> Team Explorer - > settings -> Source Control -> Check-in Policy tab ->add -> select work items -> click ok twice. You should be back at the settings screen, so now turn on check in alerts; go to “Project Alerts” in the settings menu above (the web client will launch) and tick the “Anything is checked in” check box.

Go back into toad 12.5 (set up with internal client), check a source versioned object out, make a change to a comment, check in (do not specify a work item), note toad will check the item in without warning about the policy.

Now repeat, this time specifying a work item. Check your email alert you set up earlier, and note that no work item association is mentioned in the email. Click on the changeset link in the email and observe in the web client that there is indeed a work item associated.

Now check out the same file again in Visual Studio, change the comment again, and check back in using the “Pending Changes” dialog in visual studio. Note you will receive a work item check in policy warning, now select a work item, add a comment and check the file back in. Now jump back across to your emails again, note that you will have received the check in email of your changeset, but this time the associated work item is mentioned as part of this email.


Summary:

1). Nested folder structures greater than 2 levels can’t be selected using the External client on 12.5.0.84 x64 version, but do work with the internal client.

2). It would appear that Work item association is not respecting the TFS work item check-in policy.

3). Work item association seems to handle association in a non native way, as demonstrated in the emails above. It seems that work item association appears to be happening after the changeset is checked in, not as part of the check in like Visual Studio does natively.


#8

Thanks for checking this Brian, and glad to hear it is working in the internal client. You should be able to do everything in the internal client that you
are doing using the command line. We will address the external client issue in the next beta cycle.

As you point out, the work item association is done after the check in. This is because we need to get the revision number before associating the workitem.
I don’t think a single transaction is possible with our current interface model, but would need to do some additional research.

I think you had a previous subcase open with support, can you request to reopen so that we can document the details and revisit this and the command line issue
in Toad.next.

Thanks

Stephen

From: bryan.macmillan [mailto:bounce-bryanmacmillan@toadworld.com]

Sent: Wednesday, May 14, 2014 6:01 AM

To: toadoraclebeta@toadworld.com

Subject: RE: [Toad for Oracle - Beta Discussion Forum] Check in Associations not working with Team foundation Server 2013

RE: Check in Associations not working with Team foundation Server 2013

Reply by bryan.macmillan

Hi Stephen,

After switching to the Internal Client, I can confirm the issues with multi nested folders in TFS is back to being functional again and I can check items back into TFS, and also associate work
items successfully**. Hence it would appear the issue is with the external command line client. Historically we have used the external client as older versions of toad supported more features in the external client than internal.


**One point I have noted about the work item check in association is that the work item association seems to be happening after the check-in and not at the same time/part of the check in, hence
toad will override any check in policies in force.

To demonstrate this, go into Visual Studio -> Team Explorer - > settings -> Source Control -> Check-in Policy tab ->add -> select work items -> click ok twice. You should be back at the settings
screen, so now turn on check in alerts; go to “Project Alerts” in the settings menu above (the web client will launch) and tick the “Anything is checked in” check box.

Go back into toad 12.5 (set up with internal client), check a source versioned object out, make a change to a comment, check in (do not specify a work item), note toad will check the item in
without warning about the policy.

Now repeat, this time specifying a work item. Check your email alert you set up earlier, and note that no work item association is mentioned in the email. Click on the changeset link in the
email and observe in the web client that there is indeed a work item associated.

Now check out the same file again in Visual Studio, change the comment again, and check back in using the “Pending Changes” dialog in visual studio. Note you will receive a work item check in
policy warning, now select a work item, add a comment and check the file back in. Now jump back across to your emails again, note that you will have received the check in email of your changeset, but this time the associated work item is mentioned as part
of this email.


#9

Will do, thanks for your help Stephen.