The default view of the Tracking Section currently does not display the Iteration field but does display the Points field. To view if a bug as been tagged for a particular iteration a user needs to click on the 'Edit Bug' button. It would be more useful to have the Iteration field displayed by default as it is more important than the Points field. The Points field can be hidden by default if required to make this change possible.

(In reply to Marco Mucci [:MarcoM] from comment #0) > The default view of the Tracking Section currently does not display the > Iteration field but does display the Points field. To view if a bug as been > tagged for a particular iteration a user needs to click on the 'Edit Bug' > button. > > It would be more useful to have the Iteration field displayed by default as > it is more important than the Points field. The Points field can be hidden > by default if required to make this change possible. Can you give me a couple of bugs that are good examples of this. If you're feeling ambitious, if you want to add a mockup, otherwise I can mock something after you give me examples. Also how should this feature behave for components that don't use iteration or points? -- Emma

Hi Emma, I've attached two images based on Bug 1308441. The 'Default View' images shows that the iteration field is not displayed by default when a bug is viewed. The 'Edit Bug' image shows that you need to click on the 'Edit Bug' button to see if the bug has been tagged for a particular iteration. It's important to view the iteration field when viewing a bug by default. Thanks Marco

Not every team uses the iteration field, if an iteration is not specified, should the field be displayed by default? Is this a feature that needs to be controlled at the component/product level?

I would be fine with the iteration field not being displayed if an iteration value has not been specified. Once an iteration value has been selected it should be visible the next time the bug is viewed without having to edit it. I don't believe it should be controlled at the component/product level. It's use is variable depending if the EPM or team wants to use it.