IBM Support

PM59022: RP:When there is a trace created between requirements in two externally connected projects, the author shows up as 'Unknown'.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The author shows 'UNKNOWN' when looking at revisions made to a
    requirement using cross-project traceability.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    USERS AFFECTED
    Users of Rational RequisitePro client for Windows who create
    traceability relationships between requirements in different
    projects.
    
    PROBLEM DESCRIPTION
    Consider 2 connected projects (P1 and P2).
    Users of Rational RequisitePro who create a traceability
    relationship between a requirement in P1 to/from a
    requirement located in project P2 will find that the Author
    field in the properties of the project P2 requirement shows
    the username "Unknown". This is because the requirement
    properties is updated with the local user ID who modified
    the requirement (the user ID of P1), but the user is not
    recognized by the project P2.
    
    It is important to mention that the author is correctly
    displayed in the history revision records in both
    requirements (local and external). The problem occurs when
    the project P2 requirement property is updated with the last
    user ID who modified the requirement.
    

Problem conclusion

  • Rational RequisitePro was modified to save the external user
    ID used during the connection with the external project into
    the external requirement properties as the last user who
    modify it when adding traces to/from the requirement.
    The fix for this APAR was included in RequisitePro version
    7.1.2.7 and 7.1.3.3
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM59022

  • Reported component name

    REQUISITEPRO WI

  • Reported component ID

    5724G3900

  • Reported release

    712

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-02-24

  • Closed date

    2012-06-22

  • Last modified date

    2012-06-22

  • 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

    REQUISITEPRO WI

  • Fixed component ID

    5724G3900

Applicable component levels

  • R712 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSHCT","label":"Rational RequisitePro"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.1.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
22 June 2012