When I right click the column generated by the analysis wizard, select properties, browse DXL, all options are greyed out. I cannot select "Current", and I cannot find the code used to generate the column. I am unable to see the code, nor modify it.
I need to update the code to create a skip list that skips duplicate objects created through multiple levels of linking.
If you cannot select "Current", you probably don't have the permission to write, modify or run DXL code. Contact your administrator and ask for the power "Edit DXL"
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.
We are planning to move our projects (including defect databases) to TFS. I see that I can create a work item query that spans projects, but it doesn't appear that the "quick search" field supports cross-project searches. What is the best way to accomplish this? We have "light users" that just want to come in and search for certain keywords across all projects.
In the new query editor, right click on the Project clause, and select Delete Clause. Then when you run the query, you see everything. The result doesn't have the "Project" column. You can click on Column Options, and then Select "All Projects". Then select "Team Project" and push it to the right. This will show you which project the item belongs to. Hope this is helpful.
There is no way to search across projects because Web Access always limits the search to the current project when running search query on the server.
The only solution I could suggest is to use work item queries and specify the projects explicitly.
I have team project in TFS. There are already some work items in the project. I need to add new fields to work item type. How can I do it?
Export the work item type, add the fields, and re-import it. As long as you do not delete any fields, this will not affect existing work items.
You may have to bulk-edit existing work items to put in valid values for the newly-added fields.
The best way to do this is by installing the TFS Power Tools, which will add the Process Editor to your Team menu.
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
How can I change state for dozen issues in "few clicks" in TFS? I know it is possible to export them all into Excel, do batch operation and "import" them back... (or something like this, didn't try actually).
But I am wondering if there is any quicker way to do that? For example, I would like to:
- launch some query;
- select few issues (for example, that have same 'State'='Active');
Here I would like to see some kind of dialog that display only those issue properties, that are the same. After that:
- change some field value (for example, state from 'Active' to 'Resolved');
- click 'Save'
And have each selected issue updated.
Is this possible with usual Team Explorer? I know such operation is in Telerik TFS client, but I don't like it: it doesn't allow to query issues from different projects in one time. Probably there is a simple add-on for Visual Studio that do that?
Thanks a lot!
You can use web access (the web-based front end for TFS). It supports batch updating of work items from its query results view.
Exporting to Excel is actually reasonably quick and easy. Here are the general steps (reciting from memory so may not be 100% complete):
Right click on your query in Team Explorer and select the open in Excel command (you can also do this from the query results tool window).
Update the work items in Excel as appropriate.
In Excel, select the "Team" tab on the ribbon and click Publish.
That's it!
You could use the command line: See here for an example:
http://blogs.msdn.com/b/buckh/archive/2006/09/07/tfs-power-toys-tfpt.aspx