Skip to content

Enhancement in the Capability Taxonomy merge when target has rating. #7352

@mudesmi

Description

@mudesmi

Description

The requirement is to applying the higher status of the two CT being merged.
E.g.: App_1 has CT_Old1(M – 40%-S), CT Old2(R-20%-S), CTOl3(I-40%-P) are merged into CT_New1 in the same order - Capability Taxanomy name (Inv status - Cost Allocation - Primary Flag)
Current Status:
Step#1: CT_Old1(M – 40%-S) mergers to become CT_New1(M-40%-S)
Step#2: CT_Old2(R-20%-S) mergers to becomes CT_New1(M -60%-S)
Step#2: CT_Old3(I-40%-P) mergers to becomes CT_New1(M -100%-P)

Expected change:
Step#1: CT_Old1(M – 40%-S) mergers to become CT_New1(M-40%-S)
Step#2: CT_Old2(R-20%-S) mergers to becomes CT_New1(M -60%-S)
Step#2: CT_Old3(I-40%-P) mergers to becomes CT_New1(I-100%-P)

Resourcing

We would like to add this request to the Waltz team's feature backlog

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions