Some backlogs are not display on menu 'Backlog' at TFS 2015 - tfs

I'm using TFS 2015, with Scrum process template.
I noticed that some backlogs are not displayed using menu 'Backlog' or 'Board' and are just displayed on query or search.
I'm sure that it is not related with a specific iteration. I got experiences this issues sometimes.
It makes me missing some backlogs when I organize the backlogs.
Can I get an information to solve this situation?
I'm sure that query is no problem, however some managers want to use without doing something.
For example:
normally, The backlogs are displayed as follows.
backlog: #1234 (child:#5678
bug : #5678 (parent:#1234)
However, In this case, #5678 is just displayed and #1234 isn't.
so, I have to query to see #1234 or search on #1234 If I want to see.
I hope there are displayed all backlogs on TFS normally.

Please make sure you have enabled the Show Parents and expand the tree hierarchy on the Backlog.
UPDATE:
You need to clarify your question. What's that mean for "backlog" you mentioned here? a PBI or just a bug?
If you can not see the Parents wits, then you need to enable Parents: Show.
If you mean the Bugs can not be displayed on the Backlog, then you can set the Working with bugs in SETTINGS just as you mentioned.
If you mean you cannot see other Backlog navigation levels, then just select the specific Backlog navigation level in SETTINGS- > General -> Backlogs -> Backlog navigation levels

Related

TFS unfolds PBIs in Backlog

When I refresh the Backlogview of our TFS 2017 (but the Issue was there with TFS 2015 as well), there are some Product Backlog Items, which are unfolded, showing the contained work items.
This somehow messes up the shown forecast. If I close those PBIs so that their WIs are no longer shown, the forecast disappears is not shown at all.
Is there something I might be doing wrong?
You doesn't do anything wrong and I tested in both TFS 2017 and TFS 2015 to confirm your issue. It does show like that.
This issue happens in the following situation:
Look at the pictures below, I have 2 PBIs that has child tasks. When I fold 'mmm', the 'Sprint2' forecast line won't disappear. When I fold 'jjj', the 'Sprint3' forecast line will disappear. It is hidden together with the 'Task2' under 'jjj'.
After fold:
As a workaround to solve this issue, you could drag workitems like 'jjj' to other place. Change the order of it. Do not let workitems who have child tasks show above the Sprint forecast line.

Integration of microsoft test manager with TFS for Bug management

Currently we are using TFS (Web Version) as we know a product backlog item can be added via 1-Product backlog Item 2-Bug (We are using Bug to keep track of Customer/partner logged bugs)
When ever we post a bug from MTM its visible in the product backlog list (Which we don't want)
Is there any alternates for this?
Can we create one more menu under the Backlogs tab?
enter image description here
You should really create a separate work item type, maybe "Issue", to represent an externally reported issue.
You can then triage those issues and break them down into Bugs and PBI's that then appear on the backlog for ordering.
Try and avoid the Bug as a task Anti-Pattern: https://nkdagility.com/avoid-bug-task-anti-pattern-tfs/
However you can also configure TFS to treat Bugs as Tasks, and thus they never apear on the board. Go to the Backlog and click the lower cog to configure this.
You an then create a custom "Issue" work item type for the reported stuff and add it to be shown on the Backlog.
You will need to edit the process template for this.

TFS: Why do Issues appear on the Backlog?

We are using TFS 2015 together with the CMMI process template and I have just found out that Issues do appear on the backlog if they are a child of a Feature or a Requirement work item type. If the Issue is standalone (has not link to one of the two mentioned work item types) it is not visible on the backlog.
I guess that someone has made some hacks here in order to make this possible. Originally, only Epics, Features, Requirements, Tasks, and Bugs should appear on the backlog.
I have checked the Issue work item type definition as well as the processconfiguration.xml and the categories.xml which look quite ok from my point of view.
Are there any another places where one could define which work item types should be visible on the backlog?
Thanks a lot for giving support.
To add a WIT on backlog, the three files below need to updated:
WIT Definition
Categories Definition
ProcessConfiguration Definition
You can check the required changes on this link: Add work item types to backlogs and boards to see if these changes had been applied on your project. If yes, revert these changes, then the Issue should disappear from the backlog.
You should not use the "child" link to associate with Issues.
The Parent/Child link is used for the backlog and I would think that the Issues are appearing because of this.
Try changing the Parent/Child link to Related.

Assign Backlog item to Feature

I am currently using the TFS express 2013 with update 4.
I logged in into the web portal of my TFS project where I would like to add some featues and backlog project items.
I have some trouble with displaying the backlog items under features. I have created a new feature Resignation, created a new backlog poject item Add resignation button to employee and created a link between the 2.
But in my overview I see still the following:
I would like to see it like here:
What am I doing wrong?
Your first screenshot is in the Queries tab, looking at the Results of the Assigned To Me Query. The 2nd screenshot is in the Backlogs tab.
PS - TFS Express may not contain the Portfolio Management features that you're trying to get to. I've never used TFS Express so not entirely sure which features are in there or not.

TFS 2012 scrum bug with parent as backlog item

Maybe I am not understanding the scrum development model correctly, but I am confused why TFS places bugs on a different row than my backlog item even if the backlog item is set as its parent.
I thought that we would make a bug report, and it be placed in the TO DO column. Then as you commit code to that bug, you associate the commits with that particular task ID for the bug. Then once it is done it is moved to DONE. Is that not how scrum works? What is the typical process for fixing a reported bug?
That is the view of the task board. In the most recent Scrum process template (Microsoft Visual Studio Scrum 2.x), the Bug is in the Requirements category. Doing so, the Bug is treated like a Product Backlog Item (it can be stacked ranked, broken down into workable tasks, and fed through the process like any other PBI). If you are on TFS 2012 Update 1, or TFService, you should have a Kanban board tab on the product backlog page which is where you would move your bugs through the states (New/Approved/Committed/Done). In the task board (screenshot above), the Bugs and Product Backlog Items will be shown as rows (where you have Task Here and Bug Here) and the the tasks will exist in the To do, In progress, and Done columns.
When you work against a bug, you work specifically against the tasks, and associate/resolve those tasks as you check in code. Once your 'Definition of Done' has been met, you can then move the Bug work item (on the Kanban board, or manually via the state field) to Done.
We are developing agile tools for TFS since 2008 at Urban Turtle. In the 2012 version we did exactly what you are looking for. Green line represent User Story (PBI) and red box represent bugs.
You can try our Product online if you want.
This is a print screen of the feature you requested. If you need more info just contact me. ddanis#urbanturtle.com

Resources