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.
Related
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
I setup TFS 2013 scrum template late last year and was using it without issue. When adding a new PBI or BUG on the Web Portal and tabbing into the Assigned To field I was able to start typing or drop down the list to see all the members of the Team Project.
After upgrading to TFS 2015 the list is gone and type ahead does not work. If I type the first few characters of a member and click search I am able to find a member, but this is cumbersome when going through and trying to quickly add a PBI or BUG. FYI this also happens when adding a new Bug as well as tasks on both a PBI and Bug.
Using TFS 2013, we don't seem to be able to use the History section for Work Items because it just gets clogged full of the following statements:
TFSBuild (2 days ago)
The Fixed In field was updated as part of associating work items with the build.
This is where I assume we're supposed to write history such as "tested the bug, re-opening since the following error is still occurring...". We've been putting all comments like this in the Description field though because they get lost in the history section with all the Fixed In messages.
It seems like every single build produces this Fixed In message, although it might be limited to the product backlog item - it doesn't seem consistent. Some items have about 50 of these entries and some have none.
My expectation was that these messages would only show up on the work items that the programmers referred to when committing the code. Are they possibly doing something strange when committing the code? Or is there some sort of procedure I can do to stop these messages from filling up the history entry? Thanks!
You can set "Associate Changesets and Work Items" option to "False" in your build definition to stop updating the associate work items when a build is completed.
Work items will be updated when the build with associated changeset completes and "Associate Changesets and Work Items" is set to "True". Your problem looks the same as this question:
https://serverfault.com/questions/40028/tfs-stop-team-build-process-has-updated-the-fixed-in-field-messages.
It was caused by the build wasn't completely succeed. You can refer to it to see if it can help you resolve the problem.
For more detailed information about Associate Changesets and Work Items, you can read this blog:
http://www.andygeldman.com/index.php/2011/10/ever-expanding-associated-changesets-and-work-items/comment-page-1/
In TFS 2015 when I view Timeline Tracking only a maximum of two changesets displays even though I have more changesets in the merge. It seems that only the first and last changeset will appear. I would like to see all changesets. Is there a way to configure TFS 2015 so I can see all changesets when looking at merge history via Timeline Tracking?
It will display all the changest related by default. You can see screenshot below from my TFS.
Changeset4 7 9 (There are three different folders)
Maybe the changeset which you tracked is only including two changests. You can double check it through Hierarchy Tracking.
If it is the first situation as above,the view of Timeline Tracking including only two changesets is normal.
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