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.
Related
I'm relatively new to developing with tfs (only used git before).
I'm connecting to a server, which contains a decent amount of projects.
When I create a new work item, I can select only the server below 'classification' and not the specific project.
How can I allocate a work item directly to a project instead of the server?
Thanks!
You could directly create work item under the specific team project. The simplest and effective way is through web portal.
Project--Work--New Work Item--Work Item Type
After this the a work item directly allocated to this project instead of the server.
In work item, several features depend on the team project or team that
you have selected. For example, dashboards, backlogs, and board views
will change depending on the context selected.
When you add a work item, the system references the default area and
iteration paths defined for the team context. Work items you add
from the team dashboard (new work item widget) and queries page are
assigned the team default iteration. Work items you add from a team
backlog or board, are assigned the team default backlog iteration.
You navigate to your team context from the top navigation bar.
If you are new to tfs work item, suggest you take a look at related tutorial in MSDN: Plan and track your project with work items. Besides in TFS, there is a concept of permission, also make sure your account have enough permission for the project and adding work item.
In TFS 2013, how do I mark a work item as blocked - at least at the task level, but more preferably any work item. In other sprint tracking systems it's as easy as right clicking on a work item and selecting "Blocked" and giving a reason. In TFS this doesn't appear to be so straightforward...
We use internally a tag called Blocked, and then use the Styling of the board to color the tag Red. That coloring only works on the board, and doesn't show up in queries or on the backlog, but since we use the boards during standup it works wonderfully well.
We have a story on our backlog to create a real Blocked scenario, and is also tracked on User Voice: http://visualstudio.uservoice.com/forums/330519-team-services/suggestions/2717759-visualize-blocked-task-in-task-board.
TFS relies on a flexible process model that can be customized. Out-of-the-box, there is no status Blocked in the available process models. You can customize your work item templates (tasks or others) and introduce the new status and the required transitions. After that you can set the state of your work items to the new state Blocked and set up the required queries.
See this link for a description on the available customizations.
I'd propose to apply the changes to a test environment first. Please note that changes to the work item templates might result in problems when updating your installation. See this link for details.
Interestingly, this is available in the Task work item in the CMMI template. Just copy and paste the xml from the that work item into your Scrum Process Template. Its reference name is Microsoft.VSTS.CMMI.Blocked.
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.
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.
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