index > Team Foundation Server - General > Issues List on Project Portal Problem

Issues List on Project Portal Problem

When I click on the Issues List on the project portal for my MSF for Agile site, it apparently pulls up all open work items regardless of the value for the "Issue" column. Am I missing some subtlety here?

Thanks.

Howard Pinsley

Hi Howard,

Have you been able to solve this issue? If not, please let me know and I can find help.

Thanks,
-Matt

http://blogs.msdn.com/tfs_migration/

Matthew Mitrik MSFT

Hi Howard,

You are not missing anything but it is rather a bug from our side. I will have a bug opened and we will work on fixing it in a future release.

This is due to the fact that we are rendering the Work Items report to which we are passing "IssueParam=[Work Item].[Microsoft_VSTS_Common_Issue].[Yes]"; If the cube does not contain the "Yes" dimension attribute member then the report is not defaulting the Issue Parameter and the report is rendering with the parameter set to "All (No Filter)". The default cube right after PCW contains 15 work items which issue filed is set to "No". All you have to do to work around this, it to set the issue field of one of your work items to "Yes" and run the adapters to pump data to the warehouse and rebuild the cube. Once this is done the link will start working as you would expect it.

Thanks,
Othmane

Othmane Rahmouni-MSFT

Othmane:

Thanks for the reply. I have put in work items with Yes in the Issues field. I'm new to TFS nad don't know how to "run the adapters". Is this something that is normally supposed to happen automatically? I searched the documentation and found the topic "Updating Resource Tables and OLAP Cubes". However, the section is empty?

Updating Resource Tables and OLAP Cubes
Insert introduction here.

Subhead
Insert section body here.

Can you point me in the right direction?

Thanks

Howard

Howard Pinsley

Howard,

The Adapters run automatically every hour to update the warehouse and then the Analysis Services cube is built on top of the warehouse. This process can also be called manually by invoking the Run webservice @ http://Application-Tier-Computer-Name:8080/Warehouse/v1.0/warehousecontroller.asmx

So waiting one hour should have taken care of it.

Thanks,
Othmane

Othmane Rahmouni-MSFT

Perhaps we're getting closer. I ran the web service manually and invoked the Run method. It returned true. I then invoked the GetWarehouseStatus method and it returned Idle. The report still shows the same results however...

What sets off the hourly adapter run? I don't see a SQLAgent job. Is there some other mechanism in use?

Howard Pinsley

reply 6