This wiki is locked. Future workgroup activity and specification development must take place at
our new wiki
. For more information, see
this blog post about the new governance model
and
this post about changes to the website
.
TWiki
>
Main Web
>
CmHome
>
CmCommonProperties
(07 Feb 2013,
SteveSpeicher
)
(raw view)
---+ CM Tools Common Resource Properties *[[http://spreadsheets.google.com/ccc?key=0AsgaoPBj7epTdGotZjBsY19HZTJrS3dZRDJHbExQSlE&hl=en][See Table in Google Docs]]* %TOC% ---++ Purpose This page is being used to collect information about what are common properties of change request resources of type: defect, task and enhancement. The result of this will assist in understand what properties are used for what scenarios and ensure better alignment with current implementations in defining a common CM vocabulary. Please contribute your property definitions directly into this page or create a new page and link it to here. ---++ Change Request Property Definitions For change requests of type: defect, enhancement and task Scenarios: * fixdefect - DefectScenario * plan - CmScenariosAgilePlanningOfChangeRequests * report - CmScenariosReporting * ide - ScenariosMylyn * <add more as appropriate> ---+++ Common Properties ---++++ Core Properties This is a consolidated list of most frequently used properties on a change request resource from analyzed sources attached and referenced. WG actions regarding updates to this table: * Validate that your product is accurately represented into table, update accordingly *(done)* * Identify any additional scenarios where the properties are required *(done)* * Identify any properties that you feel should (or should not) be included into the core set The approach to define the common core set of Change Request properties for OSLC-CM 2.0 will be: * Prioritization of properties based on usage in scenarios *(done)* * How many tools already support the properties *(done)* * Complexity of defining specification (Children collection of references, etc) Once a common core set is defined: * Identify if there is any existing standard vocabulary (DOAP, DC, etc) * Define the contraints on each property (open content, string with size limit, reference, complex context, etc) * Need for enumeration and value mapping: Severity, Priority, etc *[[http://spreadsheets.google.com/ccc?key=0AsgaoPBj7epTdGotZjBsY19HZTJrS3dZRDJHbExQSlE&hl=en][See Table in Google Docs]]* Work in progress for 2.0 CmResourceDefinitionsV2 ---+++ Planning Specific | *Field* | *Type* | *Description* | *Scenarios* | | DueDate | Date | | plan | | Estimate | String | Amount of work effort to complete the request in: months, weeks, days, hours | plan | | TimeSpent | String | Amount of work accomplished on the request so far | plan | | Iteration | Link | Assigned development line (Iteration, sprint, etc) | plan | | StoryPoints | String | | plan | | Implements | Link | Reference to a requirement resource that this request is implementing | plan | | Successor | Link | | plan | | Predecessor | LInk | | plan | ---+++ Sources ---++++ [[ScenariosMylyn#Task][Tasktop/Mylyn]] ---++++ [[CmCommonPropertiesCQ][Rational ClearQuest]] ---++++ [[CmChangeRequestMatrix][Rational Team Concert]] ---++++ Bugzilla [[http://www.bugzilla.org/docs/3.4/en/html/bug_page.html][Anatomy of a Bug]] ---++++ Rally Story Fields <img alt="Picture_2.png" src="http://open-services.net/pub/Main/CmCommonProperties/Picture_2.png" /> ---++++ Rally Defect Fields <img alt="Picture_3.png" src="http://open-services.net/pub/Main/CmCommonProperties/Picture_3.png" /> ---++++ Rational Change These are some common attributes from the out-of-the-box "dev_process" process. Most customer don't use it directly, but use it as a starting place for their own process. <table width="653" cellspacing="1" cellpadding="0" height="398" border="1"> <tbody><tr><th>Field</th><th>Type</th><th>Description</th><th>Scenarios</th></tr> <tr><td>problem_number</td><td>String </td><td>Unique idenitifer. Always built-in. </td><td> </td></tr> <tr><td> problem_synopsis</td><td>String <br /></td><td>One line "headline".<br /></td><td> </td></tr><tr><td>problem_description</td><td>String</td><td>Multi-line, detailed description. Can contain HTML markup.<br /></td><td> </td></tr><tr><td> severity</td><td> String</td><td>"Showstopper", "Severe", "Medium", "Minor". Values have no intrinsic value and can be changed to anything you want. </td><td> </td></tr><tr><td>priority</td><td> String</td><td> Normally1, 2, 3, 4. Can be anything.<br /></td><td> </td></tr><tr><td> request_type</td><td> String</td><td> "Enhancement, "Defect", etc </td><td> </td></tr><tr><td>product_name</td><td> String</td><td> </td><td> </td></tr><tr><td>product_version</td><td> String</td><td> </td><td> </td></tr><tr><td>modify_time</td><td> Datetime</td><td> </td><td> </td></tr><tr><td>create_time</td><td> Datetime</td><td> </td><td> </td></tr><tr><td>crstatus</td><td> String</td><td> State of the CR: entered, assigned, resolved, etc. Customers can add as many states as they want.</td><td> </td></tr><tr><td>duplicate</td><td> Link</td><td>Link to another CR submitted against the same defect or enhancement. </td><td> </td></tr><tr><td>release</td><td> String</td><td> </td><td> </td></tr><tr><td>attachment</td><td> Link (in theory)<br /></td><td>These are just attached files, but aren't currently available through OSLC with Change. I wasn't clear on if they were supposed to be supported and wasn't sure of how to model them. Should the URL directly download the file? Should it download an XML/JSON "change request" with a base-64 "data" property? </td><td> </td></tr><tr><td>resolver</td><td> String</td><td> Who the CR is assigned to. Always has the same value as "owner" unless resolver is not set--then owner is set to whoever created the CR even if it's not assigned yet. </td><td> </td></tr><tr><td>assigner</td><td> String</td><td> Who assigned the CR.<br /></td><td> </td></tr><tr><td>keyword</td><td> String</td><td>Tags. </td><td> </td></tr><tr><td> transition_log</td><td> Read-only string<br /></td><td>This uses a proprietary markup so it is not set directly. CR modifications are automatically logged to it. Comments can be appended to it by settting the _COMMENTS pseudo-attribute. When retrieved through other APIs, the markup is stripped and it's just returned as plain text with new lines. </td><td> </td></tr><tr><td> <status>_date</td><td>Datetime <br /></td><td> The date of each transition is recorded. There is no definitive "done" date, but this correspond to resolution_date or conclusion_dat. </td><td> </td></tr><tr><td> </td><td> </td><td> </td><td> </td></tr></tbody></table> ---++++ Oracle Team Productivity Center *[[http://spreadsheets.google.com/ccc?key=0AsgaoPBj7epTdGotZjBsY19HZTJrS3dZRDJHbExQSlE&hl=en][See Table in Google Docs]]* ---++++ EvoOnt BOM See : http://www.ifi.uzh.ch/ddis/evoont/2008/11/bom/doc/index.html ---++++ Helios_BT See : https://picoforge.int-evry.fr/cgi-bin/twiki/view/Helios_wp3/Web/HeliosBtOntology ---+++ Other sources Some other ontologies have been developed to represent bug reports, where some mappings were described : * http://code.google.com/p/baetle/wiki/EvoOntBomMappings for EvoOnt BOM * http://code.google.com/p/baetle/wiki/Bugtrackers2baetleMappings for BAETLE These may be reviewed in order to improve the properties for OSLC-CM.
Attachments
Attachments
Topic attachments
I
Attachment
Action
Size
Date
Who
Comment
png
Picture_2.png
manage
135.9 K
29 Sep 2009 - 22:12
MarkRinger
png
Picture_3.png
manage
142.3 K
30 Sep 2009 - 14:50
MarkRinger
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r27
<
r26
<
r25
<
r24
<
r23
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r27 - 07 Feb 2013 - 18:42:25 -
SteveSpeicher
Main
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Webs
Main
Sandbox
TWiki
Български
Cesky
Dansk
Deutsch
English
Español
Français
Italiano
日本語
Nederlands
Polski
Português
Русский
Svenska
简体中文
簡體中文
Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use
Ideas, requests, problems regarding this site?
Send feedback