[OASIS Issue Tracker] (OSLCCCM-27) New type ChangeAuthorization needed for CM spec

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/OSLCCCM-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Sarabura updated OSLCCCM-27:
-----------------------------------

    Proposal: Add a new class called "ChangeNotice" or "ChangeAuthorization".  (was: Add a new class called "ChangeNotice" or "ChangeAuthorization". Also, I think we should consider rearranging the UML diagram so that there is an abstract base class containing all the common attributes and concrete base classes inheriting from the abstract base class.)

> New type ChangeAuthorization needed for CM spec
> -----------------------------------------------
>
>                 Key: OSLCCCM-27
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-27
>             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
>          Issue Type: Bug
>          Components: Change Management
>            Reporter: Martin Sarabura
>
> Notwithstanding issue #26 which I just posted, I feel that change notice should be added explicitly to the spec.
> There are two classes of type in the current spec: Request and Task.
> Requests include Change Request (which is also drawn up as the base type in the UML diagram), Enhancement and Defect.
> Tasks include Task (which is drawn up as the base type in the UML diagram) and ReviewTask.
> A change notice in certain tools is neither a request nor a task: It is an authorization to perform multiple tasks. Thus it is more of a "command" than a request and it is a container of tasks. Since it has a different meaning than the available Types and since it is found in a number of CM tools, I believe it should be listed as its own type.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)