Every TFS default widget provided by Microsoft allows to select title, size and a query. I'd like to develop a custom widget but I didn't find the source code for the selection of a query (as show in image). Is there any example of source code in github or elsewhere?
Related
I've got a lot of product backlog items that I want to load into TFS. We've already got most of these defined in an Excel spreadsheet, so I thought that bulk importing from Excel to TFS as described here would be the best way to go.
If I just wanted a flat list, I'd be fine. Excel 2013 is a bit different than the screenshots in that article, but it worked pretty much the same. I went to the TEAM menu option and selected a new list, and then built the list from my selected query. I got a screen with my existing work items that looked like this:
According to the article I linked above, if I want to be able to add sub-tasks I need to convert the flat list to a tree list. I'm supposed to do this "by adding a tree level." However, here's the problem with that:
I've tried clicking in various cells in case something needs to be selected to "enable" this option, but my blind clicking has yielded no luck. Am I just terrible at following instructions, or does Excel 2013 have some quirk that I need to work around?
What do I need to do to enable this so that I can bulk import sub-tasks?
The Work Item Query you select needs to be a tree-based query. I'm guessing the WI Query you are selecting is a flat-list, that's why those features aren't lighting up in Excel.
To build off of Dylan Smith's answer, here's how to get your Work Item Query into a tree-based form (so you can add a tree level). This works with Team Foundation Server 2012 and higher.
Here is where to go within TFS 2012. Using the web interface, you should navigate to the query you want to load into Excel. From there, go to the 'Editor' section of the query, then there you can change the type of query to be "Tree of Work Items".
With that done, you can now load the list into Excel (using the Team tab, as described elsewhere). You can then Add Tree Levels, Add Child, etc.
I just want to get the list of all change sets of a user in TFS. I want only the id of the change set, and a link to all items which are being checked in as part of that change set.
How can I do that?
Besides option presented by Richard, you can also do that from within VS using the "Changesets" option:
It's also possible to do it via the API. I can provide a short snippet, if you're interested.
For Visual Studio 2013
Open Source Control Explorer
Right click on the repository you want to search
Select Find => Find Changesets
The "Find Changesets" window will open where you can filter by username.
tf hist ‹item› /user:name will filter the history by user, so this could be used to get a complete set of changes for a user, from which the changeset numbers can be extracted.
I found a round about way.
You can open a TFS task, and link a Changeset to the task. There you can browse for a changeset using search parameters.
I don't know why this is the only place where this functionality is available, but at least it's there.
I am in the process of evaluating JIRA as a replacement to TFS 2010.
I know that JIRA has the capability to import from CSV but cannot figure out how to export fields like the History fields from TFS to a spreadsheet.
Any recommendations / tools would be highly appreciated.
I don't think there is an easy way to do what you want.
I am thinking you would need to make your own tool using the TFS API. I don't know if JIRA has an API to do the inserting, but TFS's api is fairly good. You could easily get that data out.
For "How To" on the TFS API I usually look to Shai Raitan's TFS API blog posts.
I do custom migrations from all sorts of databases (ClearQuest, TeamTrack, Remedy) into JIRA. It takes about a week to do the job so it isn't cheap but if you have a lot of data and want more information than the standard importers provide, it's one way to go. The CSV importer probably won't do what you want.
Have a look at Appfire's Enterprise Migration Utility. It migrates TFS to JIRA, amongst others.
Simple enough, create a Query that has all your work items, click on the icon to open in Excel,
Save the Excel file as CSV.
done.
Here's what worked for me (sorry about the formatting; it was a .docx):
For every TFS Server:
Create a query by using Iteration Path for all Product Backlog Items and Bugs for every Product and/or every Scrum Team.
A single query can be used for all projects/products by altering the iteration path(s)
Format the results in TFS by selecting the appropriate columns.
Save the query, run it, and open it in Excel an .xlsx file with the word RAW included (for example, XXXX_ALL_WIs_RAW.xlsx).
Using the same file, select Save As… to create and save an excel .csv file.
Note that not all columns/mappings will be used on all projects. Delete unnecessary columns, and change column headings as needed.
The TFS columns/fields, and the Jira fields (some custom) to which they are mapped, for me were:
Iteration Path maps to Scrum Team
ID maps to Legacy ID
Work Item Type maps to Issue Type
Title maps to Summary
Description maps to Description
Acceptance Criteria maps to Acceptance Criteria
Assigned To maps to Assignee (Users must exist in Jira for this to work!)
SubCategory maps to Component/s
Effort maps to Story Points
Severity maps to Priority
Case Number maps to Case ID
Client Name maps to Customer
Platform maps to Environment
Once the .csv has been modified, use File/Check for Issues/Inspect document to determine if modification are required so the inspection results yield no issues.
Save the clean .csv as _CLEAN (for example, XXXX_ALL_WIs_CLEAN.csv).
Rename spreadsheet headers for import to appropriate Jira field names.
Field modifications:
If the work item Acceptance Criteria field has nothing in it, enter “No Acceptance Criteria in the original TFS work item” on the csv.
If the work item Description field has nothing in it, enter “No Description in the original TFS work item” on the csv.
Bugs – Severity must be converted to a number (1 through 5).
Change column headings on the .csv to match the Jira field names, as defined above in 2d.
Clean/Inspect the .csv
If necessary, increase the advanced setting jira.bulk.create.max.issues.per.import in Jira appropriately to handle the number of items being imported (there is a 250 item import limit by default).
In Jira, at the Site Admin Level – Create new Jira projects based on individual products (NOT projects!)
Create or add users that will be used in the various projects.
In Jira, at the Site Admin level – Create Custom Fields as needed
Associate new and existing custom fields to appropriate project screens, and update.
In Jira, at the Site Admin Level – Re-index DB
At the Project level – Create components for the product by using subcategory from TFS. (Can be assigned to Component Lead)
You should now be ready for import into Jira.
Test Case Migration from TFS to Jira/Zephyr if you need it:
Test case migration is a 2-part process.
The first part will get the test cases from TFS, and create and format an Excel spreadsheet containing the data that will then be imported into Jira (Zephyr).
The second part of the process will use a Java tool to import the data from the spreadsheet created in Part 1 of the process.
Part 1 – Test Case Export
Install TCExport (Used to create the Excel spreadsheet that will be used to import the test cases into Zephyr).
When mapping fields while using the .jar tool, use the Excel column letter.
Part 2 – Test Case Import
1. Download the import utility zfj-importer-utility-0.38.jar
This utility can be run by double-clicking the file in most environments. To launch the utility double-click the .jar file or run through the command prompt as: java -jar .
Detailed instructions for using the utility can be found here: https://www.getzephyr.com/insights/getting-started-zephyr-jira-importer-utility
Is there a way to look at code differential between previous and current versions of a changeset in TFS 2005/08 through a web-based interface?
I am aware of Changeset.aspx with a artifactMoniker parameter that retrieves the changeset and related files. But I would also like to view the code delta in a web based manner.
This can be achieved in TFS 2008 via the Visual Studio Team System Web Access.
First you need to open an individual Changeset details. This can be done for example by looking at a build (the Builds tab), and selecting one of the changesets associated with the build.
For some reason the version of Web Access I currently have at hand had a bug in that the link into a Changeset webpage is missing the changeset number. A quick manual fix of the URL helped.
This is the URL that is linked to
http://tfsappserver:8090/UI/Pages/Scc/ViewChangeset.aspx?changeseturi=vstfs:///VersionControl/Changeset/8695
Notice I needed to add the changeset parameter manually.
http://tfsappserver:8090/UI/Pages/Scc/ViewChangeset.aspx?changeseturi=vstfs:///VersionControl/Changeset/8695&changeset=8695
The page lists all the code files that has changed and for each file you can compare it with another version. The comparison option is available from dropdown menu on the file.
Here is what it looks like:
In VSTS 2010 – in MS Test Runner
A defect can be logged against a work item called “BUG” by default.
This bug will have all the details relevant to the test that is run like the information in the following tabs in workitem bug – details tab, System info tab , Test Cases tab, etc .,
Instead of logging defects in workitem “BUG” is it possible to log defects to any other custom workitem but still manage to hold all these details tab , system info tab , test cases tab, etc., into the custom WI.
Please refer the attachment .
You need to put your custom work item type into the Microsoft.BugCategory category. Take a look at the command line tool witadmin in %ProgramFiles%\Microsoft Visual Studio 10.0\Common7\IDE
The following blog post might help you:
VS2010 Work item categories
If you want all the controls as well (like repro steps control), then you need to make sure the appropriate fields and form controls are copied over into the work item from the Microsoft work item definitions.