Add ability to associate check ins with Work Items in TFS
Visual Studio already allows this which keeps track of which Source Control items go with which Change Control items. This would also be greatly beneficial if we could associate the database changes as well.
In the "Commit changes" windows could be nice to have the possibility to link a work item when the DB is link to TFS
Hi – this request was closed when the ‘TFS work items’ feature was released. http://documentation.red-gate.com/display/SOC3/Committing+changes
However, we’re still hearing about this enough that I’d agree with commenter Ben: it should be reopened.
We will continue to gauge interest here on UserVoice. Please do tell us more in the comments about what you expect to be able to do with Work Items in SQL Source Control.
For the first step it would be enough to get the possibility to select one of the TFS Work Item Queries and choose the corresponding work item and the state.
Ben Sproat commented
I would request this be reopened. The reason this has so many votes is the work around you list as complete is insufficient and cumbersome to use.
Would it be possible to add under the Commit-comment field a dropdown or list which shows the data of a TFS-"Team Query"?
We have implemented a "CheckIn"-Query which shows the developer his open Tasks/Bugs/... so that he can just select out of this list while checking in the pending changes.
Entering the IDs manually is annoying and most of the developers don't do it because they have to go to the TFS first, catch the ID go back to SQL Server Management Studio and write the text.
In VisualStudio this works fine - the developers just change the tab and select the item(s) and commit the changes on the "pending changes" tab.
I think the most elegant solution would be if you present the possibility to decide if the checkin will be done on TFS directly
or only on the corresponding local TFS-files. If it happens only on the local files you could see them in Visual Studio and use the
functionality there - and more than that you could check in the SQL-Code together with the VisualStudio code at once.
But then you would have to make sure that you don't loose the change-history in order to be able to deploy the changes from Development to Acceptance and Production SQL-Servers.
@alex - unfortunately due to finite development resource at our disposal even the simple things have to be prioritized alongside all the very long list of backlog items we have for SQL Source Control. We're trying our best to release as many valuable features as we can! Hope that one day we can meet your requirements!
Because of this you lost my company as a customer. Maybe we'll be back if the feature is implemented.
It's only a nice little feature, which will safe a lot of time. And I can understand, why it takes sooo long to implement, because it's only a few hours job to get workitems from the TFS.
@Anonymous - we hope to put this into v4 but this isn't due out until next year. In the meantime you can use the #R and #A syntax to do the association. Or alternatively you can use SQL Connect.
Please add it as we really want to use this technology, but the associating per work item is holding us back. We would be looking at purchasing 20-30 licenses.
The 'started' was referring to the #R #A workaround. We're still keen to implement a work-item chooser dialog, although I wouldn't think it would be implemented before the second half of the year. Could you try using SQL Connect for this? This allows you to sync from your database to a VS project, which means you can associate with workitems in the normal way when you check in. SQL Connect works against the same repository as SQL Source Control. It's in preview at the moment: http://www.red-gate.com/products/sql-development/sql-connect/
Moacir Mendonca commented
Any updates on this feature? It has been marked as "STARTED" for 2 years now?! Thanks!
Sergey Stepanov commented
# R only works with Work Item Type "Bug"?
Is there any other tag except #R and #A, for example,
#C ("Closed" state of Issue) or #D ("Done" state of Task)?
Are you working on a real UI integration with TFS Work Item?
@Remi - the #A and #R codes in the comment is the only mechanism for now. We are hoping to add a UI around this at some point, but we have no firm timescales just yet.
Remi Mongeau commented
I see that the status is "Started" with a link to an old post for a private early access release of the feature now in Sql Source Control. Are you working on a real UI integration or the status is just not up-to-date?
Vincent Salard commented
I was already aware of the parse trick but it only applies on standard WI status. A real UI integration makes more sense when we build our own status (without talking about WI lookup). I just wanted to know if it was near to be released or if a deadline was expected.
Thx for your feedback,
Tanya Joseph commented
You can associate work items using #A(Associate) and #R (Resolve) from SQL Source Control versions 1.1 and higher. The UI implementation for work items is on our list of things to do but we have not yet got around to this yet due to to various other higher priority features/issues. I will update this post once we have done the UI for this.
I hope this helps...
Vincent Salard commented
Could you give a feedback concerning the TFS WI integration improvements ?
Thx in advance,
I agree with the other comments on here. Associating it with a work item is great, but we also need to assign the other items (e.g. code reviewer) when checking in an item. These are often required by TFS and SQL Source Control just ignores those rules. Critical for us.
Thanks for the additional comments...
Jason - The free text area will actually associate the check in (commit) with the Work Item. In Visual Studio, when checking in, you can see all Work Items assigned to you and just select the appropriate Work Item from the list. We plan to implement something like this eventually, but for now, are you familiar enough with the Work Item IDs that you could just type the WI ID in manually instead of selecting from a list?
I hope this makes sense.
Alberto Silva commented
I guess we expect the default behavior associated to code check-ins, allowing for a single or multiple WI and just associate or change the WI status.
Jason McAdams commented
A free text area is not enough as it does not allow an actual association in the work item history. This is the important part. I should be able to go back to a work item and see all the changesets that have been checked in against it. I should also be able to go to a changeset, and in reverse, see the work item it was checked in against.
A check in is typically associated to one work item in our company. I have never worked anywhere that would ever need a chageset to be checked in agaisnt multiple items, but I'm sure there is a need for someone out there to do it, so I don't know how definitive that answer really is.
Association is the main concern. Resolution can be done on the work item itself. However, VS does allow an association and will resolve the item at the same time if the user selects to do so. This would just be additional functionality that could be added - as long as the user has the option to select between the two.