Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Component/s: Change Management
    • Labels:
      None
    • Proposal:
      Hide

      Create a new relationship to indicate ownership of change requests that allows the list to be ordered and that allows a contained item to belong to more than one parent if so desired.

      Show
      Create a new relationship to indicate ownership of change requests that allows the list to be ordered and that allows a contained item to belong to more than one parent if so desired.

      Description

      The current spec allows one to associated one or more change requests with the current change request either as a neutral association (relatedChangeRequest) or to inform impact analysis (affectsPlanItem) or as a decomposition (affectedByDefect). None of these relationships represents a container relationship whereby the current change request is decomposed into a series of tasks that must be done in order to satisfy the change request. This is a significant gap that can't be filled by repurposing one of the existing relationships because a) there may be a need to represent one of the other relationships in addition to a container relationship and b) there is no easy way to indicate how the client should interpret the relationship anyway. Note that task order is significant - not sure how it should be represented. Finally, there is (probably?) no need to include the same task twice on the same list. However, I can see a need for a task to show up on multiple containers so that it can be completed by the first person to get to it.

        Attachments

          Activity

            People

            • Assignee:
              jamsden James Amsden
              Reporter:
              sarabura Martin Sarabura [X] (Inactive)
            • Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: