OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-ccm message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (OSLCCCM-29) References to before and after states of affected resources


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

James Amsden updated OSLCCCM-29:
--------------------------------

    Component/s: Configuration Management
                     (was: Change Management)

> References to before and after states of affected resources
> -----------------------------------------------------------
>
>                 Key: OSLCCCM-29
>                 URL: https://issues.oasis-open.org/browse/OSLCCCM-29
>             Project: OASIS OSLC Lifecycle Integration for Change and Configuration Management (OSLC CCM) TC
>          Issue Type: Bug
>          Components: Configuration Management
>            Reporter: Martin Sarabura
>
> Our PTC tools have a usability feature that allows the end user to see the state of the affected resources prior to and after the requested changes have been implemented. This allows a reviewer to easily ascertain that the implemented changes are consistent with the request, even if other changes had been introduced by other change requests concurrently. The alternative approach - which is supported by the current spec - is to review every change in the list of change sets. This approach adds cognitive load if more than one change set was created and/or if the same resource is represented more than once in the change sets.



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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]