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.
Jason McAdams
shared this idea
We have a private early access release that allows you to Associate/Resolve Work Items on Commit. If you are interested, please see our Support Forum for full details, http://www.red-gate.com/MessageBoard/viewtopic.php?p=41213#41213.
Thank you for all your feedback and I hope this is enough for now until we implement the full feature!
23 comments
-
AdminDavid Atkinson
(Admin, Red Gate)
commented
@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!
-
alex_sefrin
commented
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. -
AdminDavid Atkinson
(Admin, Red Gate)
commented
@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.
-
Anonymous
commented
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.
-
AdminDavid Atkinson
(Admin, Red Gate)
commented
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
Hi,
# 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? -
AdminDavid Atkinson
(Admin, Red Gate)
commented
@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
Hi,
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
Hi Tanya,
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,
Regards,
Vincent. -
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
Hi Stephanie,
Could you give a feedback concerning the TFS WI integration improvements ?
Thx in advance,
Rgds,
Vincent. -
Adam
commented
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.
-
AdminBSProcurement
(Admin, Red Gate)
commented
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
Hi,
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.
-
AdminBSProcurement
(Admin, Red Gate)
commented
This is not implemented in version 1, but is very high on our priority list.
-
Justin
commented
This is a great product but all of our software check-ins in Visual Studio are goverened by TFS check-in rules including requiring a comment, work item association, and code reviewer. It would be great to be able to enforce these rules upon check-in in the future. Top priority would be work item association to add accountability for changes.
-
Chris Harland
commented
We definitely need this functionality but it goes further. We need it to comply with the policies in force for the project. eg. Checkin policies, associate with workitem policy.
-
adam rink
commented
We are looking at using RedGate source control with TFS. I agree this is a high priority for us too. We need the ability to maybe right click and see a view history, or do a diff with current version. We also need the need the ability to check in code against work items (just like Tortise SVN). So, if using DB Pro with VS, and you check in code, it will prompt you to select a work item. Also, should be a way to make comments mandatory. The reason we aren't using DB Pro is it does verification checks and never compiles our main project because of this (so that is an FYI why we need another solution).
