PM82912: [wi 252111] Baseline replacement in flow target confuses Pending Changes View

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • 'Accept' operation does not correctly accept a replaced baseline
    into DevStream.
    
    Reproduction
    
    1. Create new streams:
       - DevStream
       - TestStream
    
    2. Set TestStream as flow target for DevStream
    
    3. In DevStream add new Component 'NewComp'.
    
    4. Create new Repository Workspace DevStreamWS in DevStream and
    add some files to it.
    
    5. Show DevStreamWS's Pending Changes
       - Check in all changes
       - create a baseline 'NewBaseline' in NewComp
       - deliver change set and baseline to DevStream
    
    6. Show DevStream's Pending Changes
       - Deliver the changes in DevStream to TestStream
         => In the Component Additions dialog, select
     'Deliver component additions/removals as well as...'
    7. At this point, there should be no pending changes between
    DevStreamWS, DevStream, or TestStream
    
    8. In the Team Artifacts view, find and expand TestStream, click
    right on NewComp and 'Replace With Baseline'.
       Select '1. Initial Baseline'.
    
    9. In DevStream Pending Changes view appears two new nodes:
       'Outgoing' and 'Incoming (Replaced)'. See attachment.
       a) The 'Incoming' node is empty. You can 'Accept' this node,
    but  nothing happens as a result  << THIS IS THE PROBLEM
       b) The 'Outgoing' node contains one item: 'NewBaseline' as
    expected.
     Selecting 'Deliver' on the Outgoing node delivers the
    changes to TestStream.
     Both the 'Incoming' and 'Outgoing' nodes disappear, as
    expected.
    
    
    https://jazz.net/jazz/web/projects/Rational%20Team%20Concert#act
    ion=com.ibm.team.workitem.viewWorkItem&id=252111
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Baseline replacement in flow target confuses Pending Changes
    View
    

Problem conclusion

  • Fixed in 4.0.3
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM82912

  • Reported component name

    RATL TEAM CONCE

  • Reported component ID

    5724V0400

  • Reported release

    400

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-15

  • Closed date

    2013-08-07

  • Last modified date

    2013-08-07

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    RATL TEAM CONCE

  • Fixed component ID

    5724V0400

Applicable component levels

  • R400 PSN

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Rational Team Concert

Software version:

4.0

Reference #:

PM82912

Modified date:

2013-08-07

Translate my page

Machine Translation

Content navigation