Attributes

The criteria to be completed before a work item can be accepted.

The amount of work (in story points or hours) that was required for the work item to be completed and accepted.

The actual hours required to complete actual work.

The business value for a work item.

The user name of the person (or process) who made the most recent changes to the task, task plan, or work item.

The date and time on which the most recent concurrent changes were made to the task, task plan, or work item.

The name of the resource who initially created the task, task plan, work item, and so on.

The date on which a task, task plan, work item, and so on, was created.

The unique ID for the work item that is causing a dependency for another work item (the dependency target).

The unique ID for the work item that is affected by a dependency (the dependency source).

The description of a work item in the application, such as a task, work item, summary, and so on.

The name of the resource who has been assigned to do the actual work related to the work item.

The name of the resource who has been assigned to partner with the resource who has been assigned to do the actual work related to the work item. In Agile, this is sometimes called pair programming.

The date by which a task or work item should be completed.

The date by which a task should be finished.

The date by which a task should be started.

The amount of effort, measured in story points, required to complete all of the work associated with a work item.

The amount of effort, measured in acutal hours, that are required to complete all of the work that is associated with a work item.

The goal of a release, sprint, task plan, task, or other interval.

The name of the team member who is responsible for resolving any issues related to an impediment.

The total number of story points that have been planned for an interval.

The date on which an interval is scheduled to end.

The date on which an interval is scheduled to begin.

The unique ID for the work item.

The the type of work item. If the work item is task-based, then the list will contain task-based work item types. If the work item is activity-based, then the list will contain activity-based work item types.

The name of the JIRA filter.

The unique ID for a JIRA defect as it is actually identified in the JIRA repository. For example, DEF-001277.

The link to a JIRA defect in the JIRA repository. For example, http://jira.aod.com/defect/001277.

The name of the project in JIRA in which the JIRA defects that are associated with this project are contained.

The current status of the JIRA defect.

The user name of the person who made the most recent changes to the task, task plan, or work item.

The date on which the most recent changes were made to the task, task plan, or work item.

The name of a task (or a task plan).

The name of the investment or interval to which a work item belongs.

The work item which belongs to an investment or to an interval.

The parent of a work item.

The unique ID for the parent task.

Indicates the importance of the task in relation to other tasks. Values range from 1-5.

The name of the product.

The unique ID for the product.

The name of the product owner who has been assigned to approve the work related to the work item.

The name of the tester who has been assigned to do validate the quality of the work related to the work item.

The name of the release.

The unique ID of the release.

The amount of effort, measured in story points, required to finish all of the remaining work associated with a work item.

The amount of effort, measured in acutal hours, that are required to finish all of the remaining work that is associated with a work item.

The steps by which a defect can be reproduced by other members of a team.

The address for the location in which a resource is located. Resource Address1, Resource Address2, Resource City, Resource State, and Resource Zip Code are used together to define a resource's complete address.

The place for additional address information, if needed, for the location in which a resource is located. Resource Address1, Resource Address2, Resource City, Resource State, and Resource Zip Code are used together to define a resource's complete address.

The skills that a resource is required to have in order for them to be allocated to this work item.

The alternate name for a resource, such as a nickname.

The city in which a resource is located. Resource Address1, Resource Address2, Resource City, Resource State, and Resource Zip Code are used together to define a resource's complete address.

The email address of a resource.

The first name of a resource.

Indicates whether a resource is an active resource. An active resource must have an application license.

The last name of a resource.

The name of the skill to which a resource is most often associated.

The unique ID of the skill to which a resource is most often associated.

The state in which a resource is located. Resource Address1, Resource Address2, Resource City, Resource State, and Resource Zip Code are used together to define a resource's complete address.

The type of resource.

The unique ID for the resource.

The username of a resource.

The zip code in which a resource is located. Resource Address1, Resource Address2, Resource City, Resource State, and Resource Zip Code are used together to define a resource's complete address.

The name of the risk.

The name of the sprint.

The unique ID for a sprint.

The state of a task.

The current status of a work item, task, or project.

The group of individual resources who comprise a SCRUM team, typically a single product owner, several engineers and testers, and (occasionally) other resources, such as support, documentation, and sales.

The name of the individual resource who is the engineering lead responsible for the team that performs the actual work related to any work item completed in the sprint.

The unique ID for the group of resources who comprise a SCRUM team.

The name of the individual resource who is the quality assurance lead responsible for ensuring that any work item completed in the sprint are done to the quality standards expected by the team.

The name of the individual resource who lead an Agile team during a sprint, including running daily standup, tracking velocity, and dealing with impediments that may have been identified by team members.

The total number of story points that represents the team's velocity for the sprint.

The information about this work item that has been entered by team members.

The name of the theme that is associated with a work item.

The current, overall status of the project. In Agile, simple colors (much like a traffic light) are used to convey the current status of the project. Use red for blocked, yellow for partially-blocked, and green for not blocked. For example, if the nightly build failed or if a certain number of automated tests failed, then the traffic status may be yellow (indicating that people need to look at the nightly build reports and work quickly to address the build issues). Or, if the nightly build has failed for two or more consecutive days, then the traffic status may be red, indicating that all available persons should work together to find a resolution.

The name of the resource to whom a task or work item has been assigned.

The unique ID of the resource to whom a task or work item has been assigned.

The current state of a work item, such as Not Started, In Development, In Testing, Ready for Review, and Accepted.

Indicates whether a work item is blocked.