I (finally!) upgraded to rev 1.7.4. I had an issue with 1.6.3 where one of the milestone groups wouldn't show any of it's requirement sets. So on startup of 1.7.4 I checked and the problem has persisted across revisions. Not only that, but now other milestone groups are not showing their requiement sets. This is all under the 'Milestones' tab.
I was also amazed to see that the requirement number is no longer displayed uner the 'milestones' tab - just the short name. Without the requirement #, I loose context of those short names! Any way of getting those listed again with the short name?
I've attached some images to help you understand what's going on....
Kevin,
A couple quick things to try...
After upgrading, make sure you've deleted your browser cache - we cache the JavaScript heavily for performance so after an update, clearing the cache is needed. That could be the cause of some short names not displaying. If this doesn't work, give us a call and we'll figure out what's going on. I just tested and this shouldn't be a problem.
For the ID's in the tree - it looks like the configuration setting to display ID's in the tree is turned off, check Project, Project Configuration, Project Settings to be sure that "Display ID's in Project Navigator" is checked, the refresh the page in your browser, or click on refresh in the milestones view.
I did delete the browser cache on updgrade. It was the 1st thing I checked after configuring the system, so the cache should have been fairly clean.
I saw the checkbox for the display ID's, and that fixed part of the problem. Sometimes the short name is still not being displayed (but see my smoking comment below)
I also saw the 'show in milestones' checkbox for the folder group, which fixed the problem for the Sprint #13 milestone.
And I must be smoking something... I forgot that not all (most) of my requirements that are not on my radar screen don't have short names yet. That's why it looked so blank. And just really odd looking at first because the ID's were ON in 1.6.3 and OFF in 1.7.4.
So I think this issue is due to User Error.
