Skip to content
← Customer Feedback for Redgate

Settings and activity

2 results found

  1. Better implementation of Workitem checkin/tracking

    17 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    2 comments  ·  SQL Source Control » History/Log  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    Daniel shared this idea  · 

  2. Add ability to associate check ins with Work Items in TFS

    135 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    You have left! (?) (thinking…)
    30 comments  ·  SQL Source Control  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    under review  ·  Elizabeth Ayer responded

    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.

    Daniel supported this idea  · 
    An error occurred while saving the comment
    Daniel commented  · 

    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.