InProgress: Indicates work items that have been committed or are actively being worked on.Ĭomplete: Indicates work items that have been implemented. Proposed: Indicates work items that are new, not yet committed, or not yet being worked on. Valid values for ValueName correspond to one of the following enumerated values: Valid values for TypeName correspond to a value assigned to a STATE within the WORKFLOW section of those WITs assigned to the category group. Because the types of work items that appear on these pages correspond to the same types that appear on the product backlog page, much of the customization work that you do for the product backlog page will define the functionality of the task backlog pages.įor information about using the sprint backlog pages, see Work in sprints. Tasks must be linked to requirements using the child link type. The sprint or iteration backlog pages display both the set of requirements that you and your team have committed to in a specific iteration cycle and the tasks that you have linked to those requirements. If you use different types of work items or capture your requirements using two or more types of work items, then you can customize the product backlog page to support your usage.įor information about using the product backlog pages, see Create your backlog. Backlog items correspond to a specific type of work item based on the process template used to create your team project, such as product backlog item, user story, or requirement. The product backlog represents a list of requirements for the product that you are developing. For details, see Change access levels.įor information about using portfolio backlog pages, see Work with portfolio backlogs. Use of the portfolio pages may require you to be granted Advanced access. The product backlog displays all active items in the team's backlog. For example, Story, Goal, Initiative, or Epic.Ĭontainer element that defines the metastate mappings, default columns, and quick add panel for the product backlog page. SingularName: Specify the singular label to use when referring to the WITs associated with this backlog type. For example, Stories, Goals, Initiatives, or Epics. PluralName: Specify the plural label to use when referring to the WITs associated with this backlog type. Parent: Specify the name of the category that represents the parent portfolio backlog within the hierarchy. ![]() You use the witadmin command line tool to import and export the file.Īssign values to the attributes as described:Ĭategory: Specify the name of a category that you have defined in the categories definition file for the team project that contains the WITs to be associated with this backlog type. ![]() To update the process configuration, you export the XML definition file, edit it, and then import the file. ![]() ![]() Map metastates for tool-specific work item typesĪssign fields used in agile planning tools and charts Map metastates for a category of work item typesĬustomize the default columns and column sequenceĬhange the number of work items that can appear on the task board To learn more, see Configure and customize Agile planning tools for a team project. In addition, process configuration defines the workflow states-to-metastate mappings for all work item types (WITs) that require mapping. These tools, which you view through Team Web Access (TWA), display a filtered set of work items based on the configuration made to the PortfolioBacklog, RequirementBacklog, and TaskBacklog sections of the process configuration XML definition file. Process configuration defines the default configuration and functional capabilities that your teams can access using the Agile planning tools.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |