You are not logged in. Click here to log in.

codeBeamer ALM

Search In Project

Search inClear

Tags:  not added yet

Tracker types

Area

An area or group (parent item) including teams.


Field definitions:


Property name Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes Item ID
parent Parent Area No No
No Per status Yes Parent - child relationship between tracker items
namedPriority Priority Choice Yes No Lowest, Low, Normal, High, Highest No Same As: Name
Priority of item
name Name Text Yes Yes
No Single
Name of item
status Status Choice Yes No Active, Obsolete No Same As: Name
Yes - using workflows Status of item
color Color Color No No
No Same As: Name

Color set for breadcrumb navigation bar
submittedAt
Submitted at
Date No
No
No Same As: ID
Yes Date when the item was submitted

submittedBy

Submitted by
User No
No
No Same As: Submitted at
Yes User who submitted the item

modifiedAt

Modified at
Date No No
No Same As: ID Yes Date when the item was modified

modifiedBy

Modified by
User No No
No Same As: Modified at Yes User who modified the item

supervisor
Supervisor
Members
No No
Yes Per status
Assign subject staff according to selected target project
assignedAt Assigned at Date No No
No Per Status Yes Date when the item was assigned to a user, group, or role
assignedTo Assigned to Members No
No
Yes Per Status
User, group, or role which the item is assigned to
validFrom Valid from Date No No
No Per status
Date from which the item is valid
validUntil Valid until Date No No
No Per status
Date until which item is valid
storyPoints Story Points Integer Yes No
No Per status
Scrum story points

-- Unused 1 -- Duration No
No

No Per status


-- Unused 2 -- Duration No
No
No Per status

type Type Choice No
No
No Per status


complexity Complexity Choice No No
No Per status
Complexity of the item
resolution Resolution Choice No No
No Per status

subject Subject Choice No
No
No Per status


release Release Choice No No
No Per status

closedAt Closed at Date No No
No Per status Yes Date when the item is closed
description Description Wikitext No No
No Same As: Name
Description of the item
comments Comments/Attachments References No No
No

Comments or attachments added to items

Bug

Errors, flaws, mistakes in the product.

See more about bug tracking in Wikipedia

Field definitions:

Property name Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes
parent Parent Bug No No
No Per status Yes Parent - Child relationship between tracker items
namedPriority Priority Choice Yes No Lowest, Low, Normal, High, Highest No Per status

name Summary Text Yes Yes
No Per status

status Status Choice Yes No New, Verified, In progress, Resolved, Reopened, Closed No Per status Yes - Workflow
subject Subject Choice Yes No Requirement, Task, User Story Yes Per status
User managed reference tracker types in project
severities Severity Choice No No Blocker, Critical, Minor, Trivial No Per status

resolutions Resolution Choice Yes No Invalid, Duplicate, Works for me, Won't fix, Later, Fixed No Per status Yes - using depends on field or mandatory for special in statuses
platforms Platform Choice Yes No Platform Yes Per status
not used by default
categories Category Choice No No -- No Per status
not used by default
versions Release Choice Yes No Releases Yes Per status

submittedAt Submitted At Date Yes No
No Single Yes
submitter Submitted by User Yes No
No Single Yes Who is the submitteer
modifiedAt Modified At Date No No
No Single Yes
modifier Modified by User No No
No Single Yes Who is the modifier
assignedAt Assigned At Date No No
No Single Yes When it was assigned
assignedTo Assigned To Members Yes No
Yes Single

supervisor Owner Members No No
Yes Per status
Assign subject staff according to selected target project
categories Categories Choice No No -- No Per status
not used by default
startDate Start Date Date No No
No Per status
not used by default
endDate End Date Date No No
No Per status
not used by default
storyPoints Story Points Integer Yes No
No Per status
Scrum story points
estimatedMillis Planned effort Duration No No
No Per status
not used by default / Add estimated effort
spentMillis Spent Effort Duration No No
No Per status
not used by default / Add spent effort
spentEstimatedHours % Spent/Plan Decimal No No
No Per status Yes not used by default / Caluclated progress
description Description Wikitext No Yes
No Per status


Staff Members No No
No Per status
Assign subject staff according to selected target project

Change Request

A new feature or an enhancement to an existing feature of the product.

See more about change management: http://intland.com/blog/sdlc/change-and-configuration-management

Field definitions:

Property name Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes
parent Parent Change request No No
No Per status Yes Parent - Child relationship
namedPriority Priority Choice Yes No Lowest, Low, Normal, High, Highest No Per status

name Summary Text Yes Yes
No Per status

status Status Choice Yes No New, Verified, In progress, Resolved, Reopened, Closed No Per status Yes - using workflows
subject Subject Choice Yes No Requirement, Requirement, Use case Yes Per status
User managed reference tracker types in project
severities Severity Choice No No Small, medium, large No Per status

resolutions Resolution Choice Yes No Invalid, Duplicate, Works for me, Won't fix, Later, Fixed, Implemented No Per status Yes - using depends on field or mandatory for special in statuses
platforms Platform Choice Yes No Platform Yes Per status
not used by default
versions Release Choice Yes No Releases Yes Per status
What version it was/is fixed
assignedAt Assigned At Date No No
No Per status Yes When it was assigned
assignedTo Assigned To Members Yes No
Yes Single

submittedAt Submitted At Date Yes No
No Single Yes
submitter Submitted by User Yes No
No Single Yes Who is the submitteer
modifiedAt Modified At Date No No
No Single Yes
modifier Modified by User No No
No Single Yes Who is the modifier
supervisor Owner Members No No
Yes Per status
Assign subject staff according to selected target project
startDate Start Date Date No No
No Per status
Estimated start date of development/work (not used by default)
endDate End Date Date No No
No Per status
Estimated end date of development/work (not used by default)
storyPoints Story Points Integer Yes No
No Per status
Scrum story points
estimatedMillis Planned effort Duration No No
No Per status
Add estimated effort (not used by default)
spentMillis Spent Effort Duration No No
No Per status
Add spent effort (not used by default)
spentEstimatedHours % Spent/Plan Decimal No No
No Per status Yes Caluclated progress (not used by default)
categories Categories Choice No No -- No Per status
not used by default
description Description Wikitext No Yes
No Per status


Staff Members No No
No Per status
Assign subject staff according to selected target project

Component

Components of the product.

Field definitions:

Property name Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes
parent Parent Component No No
No Per status Yes Parent - Child relationship between tracker items
namedPriority Priority Choice No No
No Per status
not used by default
name Summary Text Yes Yes
No Per status

status Status Choice Yes No New, Released, Postponed, Outdated No Per status Yes - Workflow
categories Type Choice Yes No Government Agency, Civil Service, Company, Institution, Person No Per status

platforms Platform Choice No No Platform Yes Per status

severities Complexity Choice No No
No Per status
not used by default
versions Release Date No No
No Per status
not used by default
resolutions Resolution Choice No No
No Per status
not used by default
submittedAt Created At Date Yes No
No Single Yes Who is the submitteer
submitter Created by User Yes No
No Single Yes
modifiedAt Modified At Date No No
No Single Yes
modifier Modified by User No No
No Single Yes Who is the modifier
supervisor Supervisor Members No No
Yes Per status
not used by default
assignedAt Assigned At Date No No
No Per Status
not used by default
assignedTo Assigned To Members No No
Yes Per Status
not used by default
storyPoints Story Points Integer Yes No
No Per status Yes - Aggregation Sum/Total not used by default
estimatedMillis Unused 1 Duration No No
No Per status
not used by default
spentMillis Unused 2 Duration No No
No Per status
not used by default
description Description Wikitext No Yes
No Per status

startDate Release Date Date No Yes
No Per status

end Date Outdated On Date No Yes
No Per status

Configuration Items

Fundamental structural element of the product or system.

Field definitions:

See more about configuration items in Wikipedia

Property
name

Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes
parent Parent Configuration Items No No
No Per status Yes Parent - Child relationship
namedPriority Priority Choice Yes No Lowest, Low, Normal, High, Highest No Per status
not used by default
name Name Text Yes Yes
No Per status

status Status Choice Yes No New, Released, Postponed, Unreleased No Per status Yes - when using workflows
startDate Release Date Date No Yes
No Per status
not used by default
end Date Outdated On Date No Yes
No Per status
not used by default
submittedAt Create at Date No No
No Single
When it was submitted
submitter Created by User No No
No Single
Who is the submitteer
modifiedAt Modified At Date No No
No Single
When it was modofied
modifier Modified by User No No
No Single
Who is the modifier
supervisor Supervisor Members No No
Yes Per status
not used by default
assignedAt Assigned At Date No No
No Per Status
not used by default
assignedTo Assigned To Members No No
Yes Per Status
not used by default
storyPoints Story Points Integer Yes No
No Per status Yes - Aggregation Sum/Total not used by default
estimatedMillis Unused 1 Duration No No
No Per status
not used by default
spentMillis Unused 2 Duration No No
No Per status
not used by default
categories Type Choice No No
No Per status
not used by default
severities Complexity Choice No No
No Per status
not used by default
resolutions Resolution Choice No No
No Per status
not used by default
platforms Platform Choice No No
Yes Per status
not used by default
subjects Subject Choice No No
No Per status
not used by default
versions Release Date No No
No Per status
not used by default
description Description Wikitext No Yes
No Per status

Contact

Business contacts.

Field definitions:

Property name Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes
parent Parent Contacts No No
No Per status Yes Parent - Child relationship between tracker items
namedPriority Priority Choice No No
No Per status
not used by default
name Summary Text Yes Yes
No Per status

status Status Choice Yes No New, Released, Postponed, Outdated No Per status Yes - Workflow
categories Type Choice Yes No Government Agency, Civil Service, Company, Institution, Person No Per status

platforms Platform Choice No No
Yes Per status
not used by default
severities Complexity Choice No No
No Per status
not used by default
versions Release Date No No
No Per status
not used by default
resolutions Resolution Choice No No
No Per status
not used by default
customField[1] Address Text Yes No
No Per status
Contact information
customField[2] Zip/Postal Code Text Yes No
No Per status
Contact information
customField[3] City Text Yes No
No Per status
Contact information
customField[4] State/Province Text Yes No
No Per status
Contact information
customField[5] Country Country Yes No
No Per status
Contact information
customField[6] Language Language Yes No
No Per status
Contact information
customField[7] Phone Text Yes No
No Per status
Contact information
customField[8] Fax Text Yes No
No Per status
Contact information
customField[9] Email Text Yes No
No Per status
Contact information
customField[10] Contact Person Text Yes No
No Per status
Contact information
subjects Users Users Yes No
Yes Per status
Contact information
submittedAt Submitted At Date Yes No
No Single Yes Who is the submitteer
submitter Submitted by User Yes No
No Single Yes
modifiedAt Modified At Date No No
No Single Yes
modifier Modified by User No No
No Single Yes Who is the modifier
supervisor Supervisor Members No No
Yes Per status
not used by default
assignedAt Assigned At Date No No
No Per Status
not used by default
assignedTo Assigned To Members No No
Yes Per Status
not used by default
storyPoints Story Points Integer Yes No
No Per status Yes - Aggregation Sum/Total not used by default
estimatedMillis Unused 1 Duration No No
No Per status
not used by default
spentMillis Unused 2 Duration No No
No Per status
not used by default
description Description Wikitext No No
No Per status

startDate Valid From Date No Yes
No Per status

end Date Valid To Date No Yes
No Per status

Issue

A general tracker type, as defined by your organization if required.

Field definitions:

Property name Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes
parent Parent Issue No No
No Per status Yes Parent - Child relationship
namedPriority Priority Choice Yes No Lowest, Low, Normal, High, Highest No Per status

name Summary Text Yes Yes
No Per status

status Status Choice Yes No New, Verified, In progress, Resolved, Reopened, Closed No Per status Yes - using workflows
submittedAt Submitted At Date Yes No
No Single Yes Who is the submitteer
submitter Submitted by User Yes No
No Single Yes
modifiedAt Modified At Date Yes No
No Single Yes
modifier Modified by User Yes No
No Single Yes Who is the modifier
supervisor Owner Members Yes No
Yes Per status

assignedAt Assigned At Date No No
No Per Status Yes Assign subject staff according to selected target project
assignedTo Assigned To Members Yes No
Yes Per Status

startDate Start Date Date Yes No
No Per status
Estimated start date of development/work
endDate End Date Date Yes No
No Per status
Estimated end date of development/work
storyPoints Story Points Integer Yes No
No Per status
Scrum story points
estimatedMillis Planned effort Duration Yes No
No Per status
Add estimated effort
spentMillis Spent Effort Duration Yes No
No Per status
Add spent effort
spentEstimatedHours % Spent/Plan Decimal Yes No
No Single Yes Caluclated progress
categories Category Choice No No -- No Per status

severities Severity Choice No No Blocker, Critical, Minor, Trivial No Per status

resolutions Resolution Choice Yes No Fixed, Invalid, Won't fix, Later, Remind, Duplicate, Works for me, In Development, Implemented, Partly completed No Per status Yes - using depends on field or mandatory for special in statuses
subject Subject Choice Yes No
No Per status
not used by default
platforms Platform Choice Yes No Platform Yes Per status
not used by default
versions Release Choice Yes No Releases Yes Per status
What version it was/is fixed
description Description Wikitext No Yes
No Per status


Staff Members No No
No Per status
Assign subject staff according to selected target project

Platform

Supported product platforms.

See more about computing platforms in Wikipedia

Field definitions:

Property name Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes
parent Parent Platform No No
No Per status Yes Parent - Child relationship
namedPriority Priority Choice Yes No Lowest, Low, Normal, High, Highest No Per status
not used by default
name Name Text Yes Yes
No Per status

status Status Choice Yes No New, Released, Postponed, Unreleased No Per status Yes - when using workflows
subjects Subject Choice No No
No Per status
not used by default
categories Type Choice No No
No Per status
not used by default
platforms Platform Choice No No
Yes Per status
not used by default
severities Complexity Choice No No
No Per status
not used by default
versions Release Date No No
No Per status
not used by default
submittedAt Create at Date No No
No Single

submitter Created by User No No
No Single
Who is the submitteer
modifiedAt Modified At Date No No
No Single

modifier Modified by User No No
No Single
Who is the modifier
supervisor Supervisor Members No No
Yes Per status
not used by default
assignedAt Assigned At Date No No
No Per Status
not used by default
assignedTo Assigned To Members No No
Yes Per Status
not used by default
storyPoints Story Points Integer Yes No
No Per status Yes - Aggregation Sum/Total not used by default
resolutions Resolution Choice No No
No Per status
not used by default
description Description Wikitext No Yes
No Per status
not used by default
startDate Release Date Date No Yes
No Per status

end Date Outdated On Date No Yes
No Per status

estimatedMillis Unused 1 Duration No No
No Per status
not used by default
spentMillis Unused 2 Duration No No
No Per status
not used by default

Release

Release is a stage of development and maturity of the product available for public or private distribution.

See more about releases: Scrum and Kanban for the Enterprise

Field definitions:

Property name Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes
parent Parent Release No No
No Per status Yes Parent - Child relationship
name Name Text Yes Yes
No Per status

status Status Choice Yes No Released, Unreleased, End of life, Postponed, Delayed, In progress No Per status Yes - when using workflows
startDate Planned Start-Of-Work Date No No
No Per status
Release/Sprint start, setting is manual, but several features use for calculations - Burn down chart, Wiki Plugins etc.
endDate Planned release date Date No No
No Per status
Release/Sprint end, setting is manual, but several features use for calculations - Burn down chart, Wiki Plugins etc.
CustomField[0] Actual release date Date No No
No Per status
Real release date
CustomField[1] Planned End-of-Life Date Date No No
No Per status
End of Release support
storyPoints Story Points Integer Yes Yes
No Per status Yes - Aggregation Sum/Total
submittedAt Create at Date No No
No Single

submitter Created by User No No
No Single
Who is the submitteer
modifiedAt Modified At Date No No
No Single

modifier Modified by User No No
No Single
Who is the modifier
supervisor Supervisor Members No No
Yes Per status
not used by default
assignedAt Assigned At Date No No
No Per Status
not used by default
assignedTo Assigned To Members No No
Yes Per Status
not used by default
description Description Wikitext No No
No Per status
not used by default
versions Release Choice No No
Yes Per status
When it is set, defined releases are appearing in Planner, KanBan, Statistics list, Release in Release logic for SAFe support

Requirement

Needs of what the product should be or perform.

See more about codeBeamer RM: Requirement Management

Field definitions:

Property name Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes
parent Parent Requirement No No
No Per status
Parent - Child relationship
template Template Requirement No No Requirement No Per status
Used by codeBeamer only fore creating a new requirement based on an old one.
namedPriority Business Value Choice Yes No Nice to have, Should have, Must have No Per status

name Summary Text Yes Yes
No Per status

choiceList[0] Reached Coverage Choice Yes No Not Covered, Not Completed, No Run, Passed, Failed – Every status is allowed in accepted status, otherwise not covered can be used No Per status Yes Coverage browser / Test management uses this field
choiceList[0] Risk Choice Yes No Reference field for Risk Tracker Yes Per status
User is able to define Risks for every Requirement and using this field the Risk Matrix diagram is able to discover and diplay the Requirements on the diagram in the appropriate cell
status Status Choice Yes No New, Draft, Accepted, Waiting for Acceptance, Rejected No Per status Yes - when using workflows
categories Type Choice Yes No Folder, Functional, Non-functional, Constraint, Legal, Compatibility, Integration, Installation, Maintanability, Performance, Scalability, Security, Usability No Per status
Use Folder meaning to be able to define folders
severities Complexity Choice Yes No Blocker, Critical, Minor, Trivial No Per status
Severities for Requirements, Choice field
resolutions Resolution Choice Yes No Invalid, Duplicate,Later, Partly Implemented, Implemented No Per status Yes - using depends on field or mandatory for special in statuses
versions Release Choice Yes No Releases Yes Per status

submittedAt Submitted At Date Yes No
No Single Yes Who is the submitteer
submitter Submitted by User Yes No
No Single Yes
modifiedAt Modified At Date Yes No
No Single Yes Who is the modifier
modifier Modified by User No No
No Single Yes When it was assigned
supervisor Owner Members No No
Yes Per status
Assign subject staff according to selected target project
assignedAt Assigned At Date No No
No Per status Yes When it was assigned
assignedTo Assigned To Members Yes No
Yes Per status

subject Subject Choice Yes No -- Yes Per status
Placeholder to define references, not used by default
platforms Platform Choice Yes No Platform Yes Per status
not used by default
startDate Start Date Date No No
No Per status
not used by default, work hour measurement
endDate End Date Date No No
No Per status
not used by default, work hour measurement
storyPoints Story Points Integer Yes No
No Single
Scrum story points
estimatedMillis Planned effort Duration No No
No Per status Yes not used by default, work hour measurement
spentMillis Spent Effort Duration No No
No Per status Yes not used by default, work hour measurement
spentEstimatedHours % Spent/Plan Decimal No No
No Per status Yes not used by default, work hour measurement
CustomField[0] Color Color No No
No Per status
Defined olor for this item, Used on Planner / Cardboard
description Description Wikitext No Yes
No Per status

Risk

Tracker type for supporting Risk management - escpecially used by medical companies. Risk tracker contains all the necessary fields for easily managing risk items and risk mitigation during the project lifecycle: Hazard, Likelihood, Severity, etc. Risk tracker is bound up with the Requirement tracker via the Risk field of the Requirement tracker, this enables to manage requirement statistics according to the related risks (Risk Matrix Diagram).

Field definitions:

Property name Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes
parent Parent Risk No No
No Per status
Parent - Child relationship
namedPriority Priority Choice No No Lowest, Low, Normal, High, Highest No Per status
not used by default
name Summary Text Yes Yes
No Single

customField[1] Hazard Wikitext No No
No Single
Hazad description
customField[2] Triggering event Wikitext No No
No Single
Event description
customField[3] Harm Wikitext No No
No Single
Harm description
customField[4] Likelihood Integer No No
No Single
Likelihood value of Risk
customField[5] Severity Integer No No
No Single
Sererity value of Risk
customField[6] Risk Integer No No
No Single Cumputed Sererity value * Likelihood value by default
customField[7] Planned risk mitigation Wikitext No No
No Single
Mitigation description
customField[8] Likelihood after mitigation Integer No No
No Single
Reduced value after mitigating the risk
customField[9] Severity after mitigation Integer No No
No Single
Reduced value after mitigating the risk
customField[10] Risk after mitigation Integer No No
No Single Cumputed Reduced risk
status Status Choice Yes No New, Verified, Reduction Planned, Mitigated No Single Yes - when using workflows
categories Type Choice No No Folder No Per status
Folder is supported
severities Complexity Choice No No Blocker, Critical, Minor, Trivial No Per status
not used by default
resolutions Resolution Choice No No Invalid, Duplicate,Later, Partly Implemented, Implemented No Per status Yes - using depends on field or mandatory for special in statuses not used by default
versions Release Choice No No Releases Yes Per status
not used by default
submittedAt Submitted At Date Yes No
No Single Yes Who is the submitteer
submitter Submitted by User Yes No
No Single Yes
modifiedAt Modified At Date No No
No Single Yes Who is the modifier
modifier Modified by User No No
No Single Yes When it was assigned
supervisor Owner Members No No
Yes Per status
Assign subject staff according to selected target project
assignedAt Assigned At Date No No
No Per status Yes not used by default
assignedTo Assigned To Members Yes No
Yes Per status
not used by default
subject Subject Choice No No -- Yes Per status
not used by default
platforms Platform Choice No No Platform Yes Per status
not used by default
startDate Start Date Date No No
No Per status
not used by default
endDate End Date Date No No
No Per status
not used by default
storyPoints Story Points Integer No No
No Single
not used by default
estimatedMillis Planned effort Duration No No
No Per status Yes not used by default
spentMillis Spent Effort Duration No No
No Per status Yes not used by default
spentEstimatedHours % Spent/Plan Decimal No No
No Per status Yes not used by default
customField[0] Color Color No No
No Per status
not used by default
choiceList[0] Choice Likelihood intervals No No Unbelievable, Improbable, Remote, Occasional, Probable, Frequently No Per status Risk Matrix generator Default values for Likelihood during the Risk Matrix generation, hidden
choiceList[1] Choice Severity intervals No No negligible, marginal, critical, very critical, catastrophic No Per status Risk Matrix generator Default values for Serverities during the Risk Matrix generation, hidden
choiceList[2] Choice Risk Matrix Diagram colors No No green, yellow, red No Per status Risk Matrix generator Default color values for Risk Matrix during the Risk Matrix generation, hidden
description Situation Wikitext No Yes
No Per status
Description

Staff Members No No
No Per status
Assign subject staff according to selected target project

RPE Report

Field definitions:


Property name Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes Item ID
parent Parent RPE Report No No
No Per status Yes Parent - child relationship between tracker items
name Name Text Yes Yes
No Per status
Item name
status Status Choice Yes No New, Idle, In Progress, Successful, Error, Interrupted No Same As: Name Yes - Workflow Status of item
type Type Choice Yes No Folder No Same As: ID
Type of item
report Report Wiki Link / URL Yes No
No Same As: ID

Link to the corresponding report item
template Template Wiki Link / URL Yes No
No Same As: ID

Link to the corresponding RPE DTA file
wordStyleSheet Word Style Sheet Wiki Link / URL Yes No
No Same As: ID

Word file used as template in generation process
generatedAt Generated At Date Yes No
No Same As: ID

Date filter for the modifications of items
output Output Choice Yes No Word, PDF, HTML, Xslfo Yes Same As: ID

Output type
format Format Choice Yes No Book, Table, Ext. Table No Same As: ID

General attribute that can be used on the RPE side
orientation Orientation Choice Yes No Portrait, Landscape No Same As: ID

General attribute that can be used on the RPE side
addIdToEnd Add Id To End Choice Yes No True, False No Same As: ID

General attribute that can be used on the RPE side
useAttribAsId Use Attrib As ID Text Yes No
No Same As: ID

General attribute that can be used on the RPE side
suppressIdHeading Suppress ID Heading Choice Yes No True, False No Same As: ID

General attribute that can be used on the RPE side
headingLevelShift Heading Level Shift Choice Yes No -8, -7, -6...8 No Same As: ID

General attribute that can be used on the RPE side
oleObjects OLE Objects Choice
Yes No Inside, Outside No Same As: ID

General attribute that can be used on the RPE side
placeholderOle Placeholder OLE Choice
Yes No True, False No Same As: ID

General attribute that can be used on the RPE side
tableBorders Table Borders Choice
Yes No True, False No Same As: ID

General attribute that can be used on the RPE side
tableFontSize Table Font Size Choice
Yes No 8, 9, 10...16 No Same As: ID

General attribute that can be used on the RPE side
bilingualAttribute Bilingual Attribute Text Yes No
No Same As: ID

General attribute that can be used on the RPE side
bookSuppressNoValue Book Suppress No Value Choice Yes No True, False No Same As: ID

General attribute that can be used on the RPE side
bookObjectSeparator Book Object Separator
Choice
Yes No
True, False
No Same As: ID

General attribute that can be used on the RPE side
oleWidthLimitOn OLE Width Limit On Choice Yes No
True, False
No Same As: ID

General attribute that can be used on the RPE side
submittedAt Submitted at Date No No


No

Same As: ID
Yes Date when the item was submitted
submittedBy Submitted by User
No

No

No
Same As: Submitted At Yes User who submitted the item
modifiedAt Modified at Date
No

No


No

Same As: ID
Yes Date when the item was modified
modifiedBy Modified by User
No

No

No
Same As: Modified At
Yes User who modified the item
assignedAt Assigned at Date No No
No Per Status Yes Date when the item was assigned to a user, group, or role
assignedTo Assigned to Members No No
Yes
Per Status

User, group, or role which the item is assigned to
description Description Wikitext No Yes
No Same As: Name
Item description
comment Comments/Attachments References No No
No

Comments or attachments added to items

Task

Activities that need to be accomplished within a defined period of time.

Field definitions:

Property name Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes
parent Parent Task No No
No Per status Yes Parent - Child relationship
namedPriority Priority Choice Yes No Lowest, Low, Normal, High, Highest No Per status

name Summary Text Yes Yes
No Per status

status Status Choice Yes No New, Suspended, In progress, Partly completed, Completed No Per status Yes - using workflows
subject Subject Choice Yes No Requirement, Task, User Story Yes Per status
User managed reference tracker types in project
severities Severity Choice No No Blocker, Critical, Minor, Trivial No Per status

resolutions Resolution Choice Yes No Successful, invalid, duplicate No Per status Yes - using depends on field or mandatory for special in statuses
platforms Platform Choice Yes No Platform Yes Per status
not used by default
categories Category Choice No No -- No Per status
not used by default
versions Release Choice Yes No Releases Yes Per status
What version it was/is fixed
assignedAt Assigned At Date No No
No Per Status Yes When it was assigned
assignedTo Assigned To Members Yes No
Yes Per Status

submittedAt Submitted At Date Yes No
No Single Yes Who is the submitteer
submitter Submitted by User Yes No
No Single Yes
modifiedAt Modified At Date No No
No Single Yes
modifier Modified by User No No
No Single Yes Who is the modifier
supervisor Owner Members No No
Yes Per status
Assign subject staff according to selected target project
startDate Start Date Date No No
No Per status
Estimated start date of development/work
endDate End Date Date No No
No Per status
Estimated end date of development/work
storyPoints Story Points Integer Yes No
No Per status
Scrum story points
estimatedMillis Planned effort Duration No No
No Per status
Add estimated effort
spentMillis Spent Effort Duration No No
No Per status
Add spent effort
spentEstimatedHours % Spent/Plan Decimal No No
No Per status Yes Caluclated progress
description Description Wikitext No Yes
No Per status


Staff Members No No
No Per status
Assign subject staff according to selected target project

Team

Tracker type for teams.


Field definitions:



Property name Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes Item ID
parent Parent Area No No
No Per status Yes Parent - child relationship between tracker items
kind Kind Choice No No Team
Same As: Name
Type of item
name Name Text Yes Yes
No Single
Name of item
status Status Choice Yes No Active, Obsolete No Same As: Name
Yes - using workflows Status of item
color Color Color No No
No Same As: Name

Color set for breadcrumb navigation bar
teamEmailAddress Team email address Text No No
No Same As: Name

Team mailbox
submittedAt
Submitted at
Date No
No
No Same As: ID
Yes Date when the item was submitted

submittedBy

Submitted by
User No
No
No Same As: Submitted at
Yes User who submitted the item

modifiedAt

Modified at
Date No No
No Same As: ID Yes Date when the item was modified

modifiedBy

Modified by
User No No
No Same As: Modified at Yes User who modified the item

supervisor
Supervisor
Members
No No
Yes Per status
Assign subject staff according to selected target project
assignedAt Assigned at Date No No
No Per Status Yes Date when the item was assigned to a user, group, or role
assignedTo Team Members Members No
No
Yes Per Status
User, group, or role which the item is assigned to
validFrom Valid from Date No No
No Per status
Date from which the item is valid
validUntil Valid until Date No No
No Per status
Date until which item is valid
storyPoints Story Points Integer Yes No
No Per status
Scrum story points

-- Unused 1 -- Duration No
No

No Per status


-- Unused 2 -- Duration No
No
No Per status

type Type Choice No
No
No Per status


complexity Complexity Choice No No
No Per status
Complexity of the item
resolution Resolution Choice No No
No Per status

subject Subject Choice No
No
No Per status


release Release Choice No No
No Per status

areas Areas Choice Yes No
No Same As: Name
Area (parent item) to which the team belongs to
closedAt Closed at Date No No
No Per status Yes Date when the item is closed
description Description Wikitext No No
No Same As: Name
Description of the item
comments Comments/Attachments References No No
No

Comments or attachments added to items

Test Case

Test cases to validate and verify the product.

See more about test cases: codeBeamer QA: Test Management

Field definitions:

Property name Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes
parent Parent Test case No No
No Per status Yes Parent - Child relationship
template Template Test case No No Test case No Per status
Define Template Test Case Work Item for newly created Work Item
namedPriority Priority Choice Yes No Lowest, Low, Normal, High, Highest No Per status

name Name Text Yes Yes
No Per status

status Status Choice Yes No New, In design, Awaiting approval, Accepted, Rejected, Outdated No Per status Yes - Workflow dependent
categories Type Choice No No Folder, Compatibility, Functional, Integration, Installation, Performance, Security, Smoke No Per status
Folder is supported
severities Complexity Choice No No
No Per status
not used by default
versions Release Choice Yes No Releases Yes Per status
not used by default
submittedAt Submitted At Date Yes No
No Single
When it was assigned
submitter Submitted by User Yes No
No Single
Who is the submitteer
modifiedAt Modified At Date No No
No Single

modifier Modified by User No No
No Single
Who is the modifier
supervisor Supervisors Members No No
Yes Per status
not used by default
assignedAt Assigned At Date No No
No Per Status
not used by default
assignedTo Assigned To Members Yes No
Yes Per Status

startDate Valid from Date No No
No Per status
not used by default
endDate Valid to Date No No
No Per status
not used by default
subject Verifies Choice Yes No Bug, Change Request, Component, Requirement, Task, Use case, User story Yes Per status Checked by Coverage Browser Referenced trackers; What kind of work Items can be tested
platforms Platform Choice Yes No
Yes Per status
not used by default
CustomField[0] Pre-Action Wikitext No No
No Per status
Steps before the test steps
Table[0] Test Steps Table No No
No Per status
Test steps
|-tablecolumn[0,0] Action Wikitext Yes Yes
No


|-tablecolumn[0,1] Expected result Wikitext Yes No
No


|-tablecolumn[0,2] Critical Bool Yes No
No


CustomField[1] Post-Action Wikitext No No
No Per status
Steps after the test steps
CustomField[2] Test Parameters Wikitext No No
No Per status
Defined parameters fro Test Cases / Test Runs are multiplied
storyPoints Story Points Integer Yes No
No Per status
Scrum story points
estimatedMillis --Unused 1-- Duration No No
No Per status
not used by default
spentMillis --Unused 2-- Duration No No
No Per status
not used by default
resolutions Resolution Choice Yes No
No Per status
not used by default
description Description Wikitext No No
No Per status

Test Configuration

Test configurations define specific environment and configuration for executing/running tests.

Se more about test cases: codeBeamer QA: Test Management

Field definitions:

Property name Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes
parent Parent Test configuration No No
No Per status Yes Parent - Child relationship
namedPriority Priority Choice Yes No
No Per status

name Name Text Yes Yes
No Single

status Status Choice Yes No New, Completed (Resolved), Outdated (Closed) No Single Yes - Workflow dependent
categories Type Choice No No -- No Per status
not used by default
severities Complexity Choice No No -- No Per status
not used by default
submittedAt Created at Date Yes No
No Single

submitter Created by User Yes No
No Single
Who is the submitteer
modifiedAt Modified At Date No No
No Single

modifier Modified by User No No
No Single
Who is the modifier
supervisor Supervisor Members No No
Yes Per status
not used by default
assignedAt Assigned At Date No No
No Per Status
not used by default
assignedTo Assigned To Members Yes No
Yes Per Status
not used by default
startDate Valid from Date No No default value in completed: today No Per status
not used by default
endDate Valid until Date No No default value in outdated: today No Per status
not used by default
versions Release Choice Yes No -- Yes Per status
not used by default
milestones Milestone Choice Yes No -- No Per status
not used by default
subject Subject Choice Yes No -- No Per status
not used by default
platforms Possible configurations Choice Yes No -- Yes Per status
not used by default
storyPoints Story Points Integer Yes No
No Per status
not used by default
estimatedMillis -- Unused 1 -- Duration No No
No Per status
not used by default
spentMillis -- Unused 2 -- Duration No No
No Per status
not used by default
resolutions Resolution Choice Yes No -- No Per status
not used by default
description Description Wikitext No Yes
No Per status

Test Run

Test set (or test case) executions/runs with specific configurations.

See more about test runs: codeBeamer QA: Test Management

Field definitions:

Property name Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes
parent Parent Test run No No
No Per status Yes Parent - Child relationship
namedPriority Priority Choice Yes No Lowest, Low, Normal, High, Highest No Per status

name Name Text Yes Yes
No Per status

status Status Choice Yes No In progress(In progress), Resolved, Closed(Closed) No Per status Yes - Workflow dependent
subject Test Set Choice Yes No Test Set Yes Per status Should be defined References to Test Sets
platforms Test Configuration Choice Yes Yes Test Configuration Yes Per status Should be defined at least one References to Test Configurations
versions Release Choice Yes No Releases Yes Per status

milestones Milestone Choice Yes No Milestone No Per status

CustomField[1] Build Text Yes No
No Per status
Build number what was tested
categories Categories Choice No No -- No Per status
not used by default
resolutions Resolution Choice Yes No Passed (Completed), Failed, Blocked No Per status Coverage Browser, Test Sets check for overall statistics Result of the Test
assignedAt Assigned At Date No No
No Per status

assignedTo Assigned To Members Yes No
Yes Single
When it was assigned
submittedAt Submitted At Date Yes No
No Single

submitter Submitted by User Yes No
No Single
Who is the submitteer
modifiedAt Modified At Date No No
No Single

modifier Modified by User No No
No Single
Who is the modifier
supervisors Owner Members No No
Yes Per status
not used by default
CustomField[0] Sequential Bool No No
No Per status

Table[0] Test Cases table No Yes
Yes Per status
Collection of Test Cases
-tablecolumn[0,1] Test Case Choice Yes Yes
No


-tablecolumn[0,2] Active? Bool Yes No
No


-tablecolumn[0,3] Stop on failure? Bool Yes No
No


-tablecolumn[0,4] Result Text Yes No
No


storyPoints Story Points Integer Yes No
No Per status
not used by default
startDate Start Date Date No No
No Per status
not used by default
estimatedMillis Planned effort Duration No No
No Per status
not used by default
endDate End Date Date No No
No Per status
not used by default
spentMillis Spent Effort Duration No No
No Per status
not used by default
spentEstimatedHours % Spent/Plan Decimal No No
No Per status
not used by default
spentMillis Running Time Duration No No
No Per status Yes - Calculated field / Test Sets Test run time
severities Reported as Choice No No Bug No Per status
Found and Reported bugs
Table[1] Test step results table No No
Yes Per status
Test step results
-tablecolumn[1,1] Action Wikitext Yes Yes




-tablecolumn[1,2] Expected result Wikitext Yes No




-tablecolumn[1,3] Critical Bool Yes No




-tablecolumn[1,4] Actual result Wikitext Yes No




-tablecolumn[1,5] Result Text Yes No




description Description Wikitext No Yes
No Per status

Test Set

Test sets specify the set and order of test cases to execute.

See more about test sets: codeBeamer QA: Test Management

Field definitions:

Property name Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes
parent Parent Test set No No
No Per status Yes Parent - Child relationship
namedPriority Priority Choice Yes No
No Per status

name Summary Text Yes Yes
No Per status

status Status Choice Yes No New, In Design (In progress), Completed (Resolved), Outdated (Closed) No Per status Yes - Workflow dependent
categories Type Choice No No Folder No Per status
Folder is supported
severities Complexity Choice No No -- No Per status
not used by default
subject Subject Choice Yes No -- No Per status
not used by default
platforms Possible configurations Choice Yes No Test configuration Yes Per status Should be defined at least one References to Test Configurations
ChoiceList[0] Possible releases Choice No No Releases Yes Per status
Releases to run the tests
versions Release Choice Yes No -- Yes Per status

submittedAt Created at Date Yes No
No Single
Who is the submitteer
submitter Created by User Yes No
No Single

modifiedAt Modified At Date No No
No Single

modifier Modified by User No No
No Single
Who is the modifier
supervisor Supervisor Members No No
Yes Per status
not used by default
assignedAt Assigned At Date No No
No Per Status
not used by default
assignedTo Assigned To Members Yes No
Yes Per Status
not used by default
startDate Valid from Date No No default value in completed: today No Per status
not used by default
endDate Valid until Date No No default value in outdated: today No Per status
not used by default
CustomField[0] Sequental Bool No No
No Per status

CustomField[1] Test parameters Wikitext No No
No Per status
Defined Test parameters from Test Cases
Table[0] Test Cases table No No
No Per status
Assigned Test Cases
-tablecolumn[0,0] Test Cases choice Yes Yes test cases



-tablecolumn[0,1] Active Bool Yes No




-tablecolumn[0,2] Stop on faliure Bool Yes No




storyPoints Story Points Integer Yes No
No Per status
not used by default
estimatedMillis -- Unused 1 -- Duration No No
No Per status
not used by default
spentMillis -- Unused 2 -- Duration No No
No Per status
not used by default
resolutions Resolution Choice Yes No -- No Per status
not used by default
description Description Wikitext No Yes
No Per status

Time Recording

Recordings about individual working time spent on work items.

See more about work time management: Work Time Managememt

Field definitions:

Property name Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes
parent Parent Time recording No No
No Per status Yes Parent - Child relationship
submittedAt Submitted at Date Yes No
No Single

submitter Submitted by User Yes No
No Single
Who is the submitteer
status Status Choice Yes No Recorder, Booked No Single Yes - Workflow dependent
subjects Subject Choice Yes Yes Bug, Change Request, Issue, Requirement, Task, Test, User Story No Per status
Item to work on
namedPriority Kind Choice Yes No Analisis, Design, Implementation, Test, Approval, Administration, Organization, Other No Per status

name Activity Text Yes Yes
No Per status

startDate Date Date Yes Yes
No Per status

endDate Until Date Yes No
No Per status
not used by default
spentMillis Spent effort Duration Yes Yes
No Per status

estimatedMillis Remaining effort Duration Yes No
No Per status

categories Category Choice No No
No Per status
not used by default
severities Severity Choice No No
No Per status
not used by default
resolutions Resolution Choice No No
No Per status
not used by default
platforms Platform Choice Yes No
Yes Per status
not used by default
versions Release Choice No No
Yes Per status
not used by default
assignedAt Assigned At Date No No
No Per Status Yes not used by default
assignedTo Assigned To Members Yes No
Yes Per Status
not used by default
modifiedAt Modified At Date No No
No Single Yes
modifier Modified by User No No
No Single Yes Who is the modifier
supervisor Owner Members No No
Yes Per status
Assign subject staff according to selected target project
description Remarks Wikitext No Yes
No Per status


Staff Members No No
No Per status
Assign subject staff according to selected target project

User Story

The basic unit of work for the team is user story. The team's objective is to define, build, and test some number of user stories in the scope of an iteration and thereby achieve some even larger value pile in the course of a release. Each story has a short, incredibly intense development life cycle, ideally followed by long-term residence in a software baseline that delivers user value for years to come.

Learn more about user stories in Wikipedia.

Field definitions:

Property name Label Type List Mandatory Options Multiple Permission type System managed Business Logic
id ID Integer Yes No
No Unrestricted Yes
parent Parent User Story No No
No Per status Yes Parent - Child relationship
namedPriority Priority Choice Yes No Lowest, Low, Normal, High, Highest No Per status

name Summary Text Yes Yes
No Per status

status Status Choice Yes No ToDo, In Progress, To verify, Done No Per status Yes - using workflows
subject Requirements Choice Yes No Requirement Yes Per status
User managed reference tracker types in project
severities Severity Choice No No
No Per status
not used by default
resolutions Resolution Choice Yes No
No Per status
not used by default
platforms Platform Choice Yes No Platform Yes Per status
not used by default
categories Type Choice No No Folder No Per status
Use Folder meaning to be able to define folders
versions Release Choice Yes No Releases Yes Per status
What version it was/is fixed
assignedAt Assigned At Date No No
No Per status
When it was assigned
assignedTo Assigned To Members Yes No
Yes Per status

submittedAt Submitted At Date Yes No
No Single
When it was submitted
submitter Submitted by User Yes No
No Single
Who is the submitteer
modifiedAt Modified At Date No No
No Single
When it was modofied
modifier Modified by User No No
No Single
Who is the modifier
supervisor Owner Members No No
Yes Per status
Assign subject staff according to selected target project
startDate Start Date Date No No
No Per status
not used by default
endDate End Date Date No No
No Per status
not used by default
storyPoints Story Points Integer Yes No
No Per status

estimatedMillis Planned effort Duration No No
No Per status
not used by default
spentMillis Spent Effort Duration No No
No Per status
not used by default
spentEstimatedHours % Spent/Plan Decimal No No
No Per status
not used by default
CustomField[0] Color Color No No
No Per status
Defined olor for this item, Used on Planner / Cardboard
closedAt Closed at Date No No
No Per status Yes When it was closed
description Description Wikitext No Yes
No Per status


Staff Members No No
No Per status
Assign subject staff according to selected target project

Document View by Tracker Types

Document View is supported for the following tracker types (marked with 'YES' in Document View column):

Tracker Type Document View
Bug -
Issue -
Change Request YES
Component YES
Configuration Item YES
Contact YES
Platform -
Pull Request -
Release -
Requirement YES
Risk YES
RPE Report YES
Task YES
Team -
Test Case YES
Test Configuration -
Test Run -
Test Set -
Time Recording -
User Story YES

Please note that availability of Document View feature also depends on license.