Settings and activity
3 results found
-
135 votes
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.
An error occurred while saving the comment An error occurred while saving the comment 
Jason McAdams
commented
Thanks for your reply. My guess is you are going to find almost all TFS users will at least want this functionality. The whole draw to TFS is the fact it does source control, version control, and change control. This feature is what integrates the source control and the change control in TFS for Visual Studio. I do understand that it's not the highest priority since everything should be working first, but I think it should be in the RTM.
Jason McAdams
shared this idea
·
An error occurred while saving the comment Jason McAdams
commented
Unlike the history and/or difference ideas being added to the interface which can still be checked in Visual Studio, this functionality can only be used if added to the interface directly. I believe this is a pretty important enhancement for most TFS users whi use if for Change Control as well. It already allows for a Comment on commit which is great (and which we'll use in the meantime to enter the TFS Work Item #), but an associated work item would be even better.
-
47 votesJason McAdams
supported this idea
·
-
189 votes
While SQL Source Control provides a way to view object history, it does require additional tooling to update your database to a specific version from history.
We currently have documentation on how this works here: https://documentation.red-gate.com/soc/common-tasks/update-to-a-revision-from-source-control
Jason McAdams
supported this idea
·
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.