关于TFS导出至Excel时Closed/Resolved状态任务未导入的技术咨询

Let’s walk through the most likely gaps in configuration or workflow that could be causing your Closed/Resolved tasks and user stories to fail to show up in Excel—even though they appear in your TFS queries:

• Double-check the query used for the Excel import
  When you connect Excel to TFS, you either use a saved query or build one during the import process. It’s common for default queries (like "Active Work Items") to exclude Closed/Resolved states by default. Open the query in TFS, head to the Filter tab, and verify the State field is set to include all states, or explicitly lists Closed and Resolved alongside active states. If the query filters these out, Excel will never pull them in.

• Audit the Excel import wizard settings
  During the import flow, there’s a step where you can refine results—and it’s easy to accidentally add a hidden filter that blocks closed/resolved items. Re-run the import (or edit your existing connection) and pay close attention to two key steps:

  • Make sure the State column is selected in the Choose columns section (if it’s excluded, you won’t see those entries even if they’re imported)
  • Confirm no extra filter is applied to the State field that limits results to only active states

• Verify permissions for the import account
  Even if you can see the closed/resolved items in TFS, the account used to run the Excel import (your own, or a service account) might lack permissions to view work items in those states. In TFS, go to Project Settings > Permissions, locate the relevant user, and ensure they have the View work items in this node permission enabled for all project areas. Some setups restrict access to only active work items, which would block closed entries from being pulled into Excel.

• Check incremental refresh configurations
  If you’ve set up Excel to refresh data incrementally (to save time), it might miss updates where work items transitioned to Closed/Resolved. In Excel, go to the Data tab, find your TFS connection, and disable incremental refresh temporarily. Run a full refresh—if the closed items appear, you’ll need to adjust the incremental refresh rules to include state changes.

• Ensure query groups are expanded in TFS
  If your TFS query uses grouping (e.g., grouping by State), make sure the Closed/Resolved groups are expanded when you save the query. Collapsed groups can cause Excel to import only group headers instead of individual work items. Open the query in TFS, expand all groups, re-save it, then refresh your Excel data.

• Validate plugin compatibility
  Older versions of the Excel TFS plugin (or Azure DevOps Office Integration) can have bugs that prevent closed/resolved states from syncing properly. Check for updates to the plugin—newer releases often fix compatibility issues with state transitions in TFS.

内容的提问来源于stack exchange，提问作者Jan Buelens