Next in thread → Next in month →

[OASIS Issue Tracker] (OSLCCCM-24) Moving ChangeRequest properties to subclasses could create incompatibilities

From
OASIS Issues Tracker <>
Date
2016-08-29T17:58:17+00:00
ID
Thread
[OASIS Issue Tracker] (OSLCCCM-24) Moving ChangeRequest properties to subclasses could create incompatibilities
[ https://issues.oasis-open.org/browse/OSLCCCM-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Crossley updated OSLCCCM-24:
---------------------------------

    Component/s: Change Management

> Moving ChangeRequest properties to subclasses could create incompatibilities
> ----------------------------------------------------------------------------
>
>                 Key: OSLCCCM-24
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-24
>             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
>          Issue Type: Bug
>          Components: Change Management
>            Reporter: James Amsden
>
> CM 2.0 only defined oslc_cm:ChangeRequest and all the CM properties were properties of that class. 
> CM 3.0 introduces a standard set of subclasses of ChangeRequest including Defect, Enhancement, ReviewTask and Task. 
> Currently the CM 3.0 spec moves ChangeRequest property tracksRequirement to ReviewTask and implementsRequirement to Enhancement. This could be a breaking change if CM 2.0 clients no longer see these properties on a ChangeRequest.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
Next in thread → Next in month →