Integrate
Clarity
with Rally

ccppmop1581
If your organization is using Clarity to manage investments and their associated funding, and Rally for Agile development and execution, the Clarity/Rally integration helps bridge the informational gap between investment planning and execution. Oftentimes, reports are used to aggregate data from multiple systems, or spreadsheets, to correlate information related to both investment planning and the actual product delivery or execution status of the work itself.
With this integration, you can,
  • Align a Rally Initiative with a single Clarity Project.
  • Associate multiple Rally initiatives with a single Clarity Project.
  • Fund and track execution across multiple Rally teams.
  • Obtain work details such as features and user stories, from Rally within Clarity.
  • Synchronize data bi-directionally to monitor execution activities in either Clarity or Rally.
  • Track actuals within Clarity against Rally features and user stories.
With the Clarity-Rally integration, you will obtain the following benefits:
  • Transparency
    : At the project or investment-level in Clarity, you have visibility of (but not limited to) execution status, completed work, remaining effort. You will also be able to have an understanding of how the teams’ efforts are aligned with the organizational goals.
  • Efficiency
    : Once you have transparency across your organization, you can streamline the work and reduce waste by building the right things at the right time. You can optimize the flow of value, improve quality, align resources to business priorities, and drive continuous improvement.
  • Scope management
    : With the visibility into the project execution details, you are able to better manage the scope of projects. Based on data, you can decide whether you want to adjust the scope to meet the timelines.
  • Delivery Tracking
    : You can now assess whether a project will complete on time or is at risk of spillover. For example, if a project’s GA date is in a week and there is one month’s worth of work pending, it is unlikely to release on time. You can then decide to either move the delivery timeline or reduce the scope to meet the date.
2
Integration Scenario
Consider a simple scenario. A product development organization uses Clarity for funding and tracking project status, and Rally for agile development and execution. The organization decides to integrate the two systems to keep them in sync and get visibility into the project execution. After the integration is configured, data between Clarity and Rally flows as follows:
  • Business units define a Clarity project for each initiative that they want to fund.
  • Once the funding for a project is approved, the Project Manager ties an integration process for the project in Clarity.
  • The Project Manager triggers the synchronization job in Clarity to create a corresponding initiative in Rally.
  • Product Managers create features and assign teams in Rally.
    Note: The integration can also be configured to do bidirectional synchronization. This allows teams to create features in either system and have the work items synchronized to the other system.
  • When the synchronization job runs next time (either scheduled or manually triggered), the features and user stories under the Rally initiative are brought over to Clarity as tasks.
  • The execution status at the feature-level is also synchronized, giving complete visibility into the initiatives as shown in the illustration below:
Plan the Integration
Before integrating Clarity with Rally, you need to analyze your current setup and decide the integration option that best suits your environment.
Decide the Integration Type
Clarity supports two types of integration with Rally. Depending on how Clarity and Rally are implemented in your organization, decide the option you want to choose.
Portfolio Items Integration
With this integration type, you will be able to:
  • Link a Clarity project to a single parent portfolio item (such as an initiative) in Rally. You can associate only one parent portfolio item with a Project.
  • Bring over the corresponding child portfolio items (such as features) as tasks in Clarity.
  • Bring over the execution status of the corresponding features to Clarity.
  • Track the execution status of the project from Clarity. You can only track two levels of portfolio items with this integration type. For example, you can track the progress of an initiative and its corresponding features.
Investments Integration
With this integration type, you will be able to:
  • Link a Clarity project to a single Rally investment. The investment can include features that cut across multiple initiatives or any other parent portfolio item.
  • Bring over features from multiple initiatives that are tied to the investment, as Tasks in Clarity.
  • Track multiple initiatives and multiple levels of portfolio items such as initiative, epic, feature, sub-feature, and so on from Clarity.
You can configure both types of integrations (portfolio items and investments) for the same Rally workspace; however, a single Clarity project can only be associated with one integration type. With either type, any user stories from the features can also be configured to be brought in as subtasks in Clarity. Only Clarity projects which are configured to sync user stories will bring in user stories from Rally.
Decide the Integration Type
The integration direction determines which system is updated during synchronization. The option of selecting the integration direction is only available for the Portfolio Items integration type.
For investment integration type, the direction is always set to Rally to Clarity. You can synchronize Clarity projects with Rally portfolio items in the following directions:
Direction Option 1: Rally to Clarity
  • Clarity projects are created as initiatives in Rally.
  • Features under the Rally initiatives are created as corresponding tasks under the linked Clarity projects.
  • Access the status information imported from the Rally portfolio items into the corresponding Clarity project and tasks.
Diagram depicting how the objects are synchronized in the Rally to Clarity direction
In this integration direction, the mapping of the Rally portfolio items to Clarity projects does not have to be contiguous to the portfolio items mapped to Clarity tasks.
For example, if your portfolio item hierarchy in Rally includes initiatives, epics, and features, then you can map the items as follows:
  • Rally initiatives to Clarity projects
  • Rally features to Clarity tasks
In this example, you can skip mapping anything to the epic level portfolio item in Rally.
Direction Option 2: Clarity to Rally
  • Clarity projects are created as initiatives in Rally.
  • Selected tasks under the linked Clarity projects are created as corresponding features under the Rally initiatives.
  • The project manager has access to status information imported from the Rally portfolio items into the corresponding Clarity project and tasks.
Direction Option 3: Bidirectional
  • Clarity projects are created as initiatives in Rally.
  • Features under the Rally initiatives are created as corresponding tasks under the linked Clarity projects.
  • Selected tasks under the linked Clarity projects are created as corresponding features under the Rally initiatives.
  • The project manager has access to status information imported from the Rally portfolio items into the corresponding Clarity project and tasks.
  • Integration with Rally Portfolio Items
    : This integration type allows your organization to maintain the operational activity in Rally SaaS and use
    PPM (versión clásica)
    to focus on project status. This integration type allows you to link
    Clarity
    projects to parent portfolio items such as Initiatives in Rally. You can also link
    Clarity
    tasks to child portfolio items such as Features in Rally. An initiative can cross multiple features and releases has a start and end date, and rolls up work beneath it. You can define features under the initiatives and can associate them with releases.
  • Integration with Rally Investments
    : Use this integration type to define your business strategies in
    PPM (versión clásica)
    and execute the work in Rally SaaS. This integration type allows you to define investments in Rally with a start date, finish date, and other minimum details. You can then map portfolio items at the lowest level (the default being features) from different Rally investments. This type of integration does not require that you map initiatives. The features, or items at any other level in the hierarchy, from the investments, are brought over to
    PPM (versión clásica)
    as tasks. Users can configure which portfolio item hierarchy levels they want to bring into
    Clarity
    as tasks.
You can create both types of integrations (portfolio items and investments) in the same Rally workspace; however, a single
Clarity
project cannot synchronize to both portfolio items and investments. With either type, any user stories from the features can also be configured to be brought in as subtasks in
PPM (versión clásica)
. Only
Clarity
projects which are configured to sync user stories will bring in user stories from Rally.
icon_beta.png
The new investment-level integration is considered a beta feature and is not available with on-premise editions of Rally. The basic authentication required for Rally on-premise edition users that want to use the investment integration type does not provide the full functionality that is exclusively available with
Clarity
integrations with Rally SaaS. To support Rally SaaS integrations,
Clarity
can leverage its API Key authentication instead of basic authentication.
Integration Components
Integrate Portfolio Items
Integrate Investments
Integration Subpage
: Configure the integration policy for portfolio items.
Integration Subpage
: Configure the portfolio item hierarchy for Rally investments.
Background Job
: Synchronizes
PPM (versión clásica)
projects with Rally portfolio item updates.
Two (2) Background Jobs
:
  • Job 1
    creates Rally investments from
    PPM (versión clásica)
    projects.
  • Job 2
    synchronizes
    PPM (versión clásica)
    projects with Rally investment updates.
Agile Summary project and task properties:
The
PPM (versión clásica)
project is linked with the Rally portfolio items.
Agile Summary project and task properties:
The
PPM (versión clásica)
project is linked with the Rally investment.
Timesheet Integration
: Embedded
PPM (versión clásica)
Timesheet portlet in Rally
Timesheet Integration
: Embedded
PPM (versión clásica)
Timesheet portlet in Rally
Integration Benefits
Integrate Portfolio Items
Integrate Investments
Project Managers can answer the following questions for a release
:
  • Has it been approved as part of the portfolio governance process?
  • How much is the cost?
  • Are we on track?
  • What gets delivered?
At the enterprise level, the integration provides the following benefits
:
  • Portfolio visibility for business stakeholders so they are aware of investment benefits and delivery
  • Elimination of redundancy by seamlessly managing project artifacts between
    PPM (versión clásica)
    and Rally
  • Project status information and visibility so budget, resource requirements, and deliverable status are available in
    PPM (versión clásica)
  • Fund and plan investments based on business initiatives
    . Link a
    PPM (versión clásica)
    project directly to a Rally initiative in the portfolio hierarchy.
  • Fund and track the execution of investments across multiple projects (teams)
    . Use a
    PPM (versión clásica)
    project to fund and track work across multiple Rally teams. The projects fund the same initiative.
  • Plan for work based on iterative funding cycle
    . Use a
    PPM (versión clásica)
    project to track multiple iterative funding cycles.
  • Complete traceability from planning to actual execution of investments
    . You can track actual time for feature tasks using
    PPM (versión clásica)
    Timesheets.
  • Manage resource capacity
    . You can manage resource capacity for user stories using
    PPM (versión clásica)
    project staffing.
Integration Directions
You can synchronize agile
PPM (versión clásica)
projects with Rally portfolio items in the following directions:
Direction Option 1: Rally to
Clarity
  • Link agile projects in
    PPM (versión clásica)
    to corresponding agile integrations with Rally.
  • PPM (versión clásica)
    projects are created as
    initiatives
    in Rally.
  • Features under the Rally initiatives are created as corresponding
    tasks
    under the linked
    PPM (versión clásica)
    projects.
  • Access the status information imported from the Rally portfolio items into the corresponding
    PPM (versión clásica)
    project and tasks.
In this integration direction, the mapping of the Rally portfolio items to
PPM (versión clásica)
projects do
not
have to be contiguous to the portfolio items mapped to
PPM (versión clásica)
tasks.
For example, if your portfolio item hierarchy in Rally includes initiatives, epics, and features, then you can map the items as follows:
  • Rally initiatives to
    PPM (versión clásica)
    projects
  • Rally features to
    PPM (versión clásica)
    tasks
In this example, you can skip mapping anything to the epic level portfolio item in Rally.
Direction Option 2:
Clarity
to Rally
  • The project manager links agile
    PPM (versión clásica)
    projects to corresponding agile systems. Each agile system is configured as an integration to Rally.
  • PPM (versión clásica)
    projects are created as initiatives in Rally.
  • Selected tasks under the linked
    PPM (versión clásica)
    projects are created as corresponding features under the Rally initiatives.
  • The project manager has access to status information imported from the Rally portfolio items into the corresponding
    PPM (versión clásica)
    project and tasks.
Direction Option 3: Bidirectional
  • The project manager links agile
    PPM (versión clásica)
    projects to corresponding agile systems. Each agile system is an integration configuration to Rally.
  • PPM (versión clásica)
    projects are created as initiatives in Rally.
  • Features under the Rally initiatives are created as corresponding tasks under the linked
    PPM (versión clásica)
    projects.
  • Selected tasks under the linked
    PPM (versión clásica)
    projects are created as corresponding features under the Rally initiatives.
  • The project manager has access to status information imported from the Rally portfolio items into the corresponding
    PPM (versión clásica)
    project and tasks.
Example: Integrate an Agile Project in
PPM (versión clásica)
with Rally
A product development team uses
PPM (versión clásica)
and a separate tool to track their software development projects. As more teams embrace agile methodologies, project management receives limited insight into team effort. Visibility is suffering both at the program and portfolio levels. Entering time twice in two different systems is leaving developers frustrated. Leadership at the portfolio level finds it difficult to track the business value of these agile projects.
Management decides to integrate their
Clarity
projects with Rally portfolio items. Project managers can now manage and track all agile projects as initiatives. The scrum teams can create features, user stories, and tasks to define their work. The initiative and feature status details are synchronized back to
PPM (versión clásica)
as project and task agile summaries.
Configure the Integration Between
Clarity
and Rally
Project data is integrated between the two systems based on the following setup:  
  • Integration object and its attributes that are defined to create the connection with Rally.
  • An agile integration owner with access to projects, resources, and API.
  • Project-level settings for synchronization.
  • A background job that runs to synchronize project data.
As an administrator, complete the following high-level steps to connect the product with Rally: 
4
4
Verify the Prerequisites
To integrate with Rally, complete the following requirements:
  • Install the compatible version of the Agile add-in on your
    PPM (versión clásica)
    product instance:
    Installing the add-in allows you to save the integration information and populate default integration values. See the Release Notes for the requirements
    .
  • Install the Agile add-in content:
    Navigate to the
    Items
    tab for the Agile add-in under
    Administration
    ,
    Studio
    ,
    Content Add-Ins
    and verify that all the listed items that were
    Upgrade Ready
    are now showing the
    Installed
    status.
  • Enable the REST API on your system so the Synchronize Rally job can run:
    Navigate to
    Administration
    ,
    General Settings
    ,
    System Options
    to verify the REST API status. The job uses the REST APIs to synchronize data between the systems. 
  • Define an active
    PPM (versión clásica)
    user as the Agile Integration Owner:
    The user needs the appropriate access rights to update the projects and tasks in the integration.
On-Premise customers can follow the steps in Add-Ins and Integrations to learn how to install the Agile add-in. SaaS customers must create a support ticket to request the Agile add-in installation. During the Agile add-in installation, attributes are created in the Project and Task objects. The new attributes are protected and you cannot add, modify, or delete them from the data warehouse.
Define the Integration Attributes
Configure the integration attributes available with the Agile add-in to create a connection with Rally. Define the information necessary for the integrated systems to work together. Also, capture the default integration information that is needed for transferring data.
Follow these steps
:
  1. Click
    Administration
    ,
    General Settings
    ,
    Integrations
    .
  2. Click
    New
    .
  3. Create an integration with Rally by defining the following fields:
    • Integration URL:
      Defines the URL for the integration instance (for example, the Rally instance URL). To determine what URL to use when connecting to Rally from behind a firewall, refer to the Rally documentation for alternate URLs and associated IP addresses.
    • Integration Instance:
      Defines the integration instance to connect to such as a Rally workspace ID. See
      Get the Rally Workspace ID
      in Get Rally Integration ID Values.
      The Integration Instance field requires a value to create a successful integration with Rally. The Synchronize Rally job uses the value in this field to synchronize
      PPM (versión clásica)
      projects with Rally investments and portfolio items. The job fails if a value is missing from the field.
    • Referrer URL
      Defines the identity provider URL for use by the
      PPM (versión clásica)
      timesheet integration with Rally. The value in this field is used only if you are not using the same URL as the
      Integration URL
      field. See Configure SSO for
      Clarity
      Timesheet Integration with Rally
      .
    • Authentication Type
      • Basic:
        Select this authentication method for legacy integrations with Rally On-Premise (no longer supported). Provide a username and password to use for authentication. When using this authentication type, do not specify an API key. Basic integrations cannot use an API key.
      • API Key:
        Select this authentication method to integrate with Rally On Demand. Provide the Rally API Key that maps to the
        PPM (versión clásica)
        integration record. To obtain this key, follow the directions on this page. We recommend that you create a unique API Key for each Integration record in
        PPM (versión clásica)
        . The API Key is associated with a  Rally user that has the required privileges to update the Rally workspace. Whenever you synchronize information from
        Clarity
        to Rally, the updates appear for the Rally user that is associated with the API Key. Even though the username and password fields appear, values are not needed when using this authentication type.
  4. (Optional) To connect to Rally using a proxy server in a
    PPM (versión clásica)
    on-premise environment, specify the following proxy server information. If you are accessing Rally through a non-authenticated proxy, provide the proxy server and port details only. If you are accessing Rally through an authenticated proxy, also provide the proxy username and password. After defining the proxy server information, restart the
    PPM (versión clásica)
    app and bg services.
    • Proxy Server:
      Defines the name of the proxy server. Provide the full URL starting with http or https.
    • Proxy Port:
      Defines the port for the proxy server.
    • Proxy User Name:
      Defines the user name for connecting to the proxy server.
    • Proxy Password:
      Defines the password for connecting to the proxy server.
      If you do not have the proxy server information, contact your network administrator. If the connection to Rally is unsuccessful, review the proxy server logs to make sure the IP address is allowed.
  5. Click
    Save
    .
    A new
    Rally
    tab appears next to
    General
    . The new tab appears only if the Agile add-in is installed.
  6. Click
    Rally
    . For
    Integration Type
    , select one of the following options:
    • Select
      Investment
      to integrate with Rally investments. The
      Portfolio Item Hierarchy
      tab appears.
      image2018-11-20_17-35-46.png
    • Select
      Portfolio Item
      to integrate with Rally portfolio items. The
      Integration Policy
      tab appears.
      image2018-11-20_17-36-5.png
  7. Create the following defaults for tasks:
    • Task Open for Time Entry:
      Specifies that the tasks created in
      PPM (versión clásica)
      are open for time entry. If you do not select this option, the default setting from the task object definition takes effect.
    • Task Cost Type:
      Defines the default cost type value to use when a task is created in
      PPM (versión clásica)
      . The default value is used only for task creation, not for updates.
    • Task Charge Code:
      Defines the default charge code value to use when a task is created in
      PPM (versión clásica)
      .
  8. Click
    Save
    .
  9. Depending on the type of integration you create, complete one or both of the following tasks:
    1. To integrate with Rally investments, complete the steps described in
      Define the Portfolio Item Hierarchy
      .
    2. To integrate with Rally portfolio items, complete the steps described in
      Define the Integration Policy
      .
When a parent
Clarity
task has actuals, assignments, or both, the integration cannot add a child task under this parent. Instead, the integration adds the child task without a parent. The behavior complies with the rule that summary tasks in
Clarity
cannot have actuals or assignments. The situation applies when synchronizing user stories or portfolio hierarchy items from Rally to
Clarity
tasks.
Verify the
Clarity
URL Appears in Rally
  1. Log in to Rally.
  2. Click
    Setup
    from the top right in the navigation bar.
  3. Click the
    Workspaces & Projects
    tab.
  4. To the right of the workspace click
    Edit
    .
  5. On the
    Edit Workspace
    page, scroll down to the
    Integrations
    section.
  6. Verify the correct
    PPM (versión clásica)
    URL appears in the
    Clarity
    URL field. After you define the integration in
    PPM (versión clásica)
    , the
    Clarity
    URL field is populated in Rally.
    Rally generates
    PPM (versión clásica)
    fields for the integrated investment work item type.
    image2018-12-4_12-46-30.png
Define the Portfolio Item Hierarchy (Investment-Level Integrations Only)
If you are integrating with investments, complete the steps in this section.
On the
Portfolio Item Hierarchy
tab, specify the portfolio items and their hierarchy levels or ordinals that you want associate with Rally investments.
The integration uses the Ordinal field values as follows:
  • Associates a portfolio item type with a position in the portfolio item hierarchy.
  • Determines which Agile Summary page to display for the tasks.
  • Determine the type of work item or portfolio item allowed for parents and children.
The Ordinal field value starts with 0 for the lowest level of portfolio item (such as Feature), and increments by 1 for each portfolio item type as you go up in the hierarchy. As an administrator, you are responsible for creating the portfolio hierarchy data in
PPM (versión clásica)
.
Follow these steps:
  1. Click
    New
    to create one row for each level in the portfolio item hierarchy that exists in the Rally workspace. You can add, delete, or update levels.
  2. Enter the portfolio item type name such as epic, initiative, or feature. The value must match exactly the portfolio item type name in the Rally workspace.
  3. Enter the portfolio item type hierarchy level or ordinal as it is defined in the workspace. See
    Get Portfolio Item Type Ordinals
    in Get Rally Integration ID Values.
  4. (Optional) Select the
    Create and Sync Portfolio Items
    flag to bring the portfolio item level to
    PPM (versión clásica)
    as a task when the sync job runs. Select only the levels that are needed. You can skip levels in the hierarchy.
Define the Integration Policy (For Portfolio Item Integrations Only)
If you are integrating with portfolio items, complete the steps in this section.
The documentation reflects a Rally portfolio hierarchy that is available and supported by default.Rally allows you to configure up to five levels of portfolio items in the portfolio hierarchy. The lowest level is P1 and the highest level is P5. As per the default configuration, you can map to a maximum of two portfolio items at any hierarchy level. For example, you can map to feature at the P1 level and initiative at the P2 level. In
PPM (versión clásica)
, the P1 level item is mapped to a task and the P2 level item is mapped to a project.
We recommend that you do not change the value for the
Portfolio Item Type Map
fields for projects and tasks after the initial synchronization. Changing either value can break the connection with Rally.
Follow these steps
:
  1. On the
    Integration Policy
    tab, define the following integration policy details:
    • Portfolio Item Type Map (Project):
      Defines the portfolio item type that you want to map to
      Clarity
      projects (for example, initiative). You can map a project to any level in the portfolio hierarchy except the P1 level. We recommend that you do not change the value for this field after the initial synchronization. Changing this value can break the connection with Rally.
    • Portfolio Item Type Map (Task):
      Defines the portfolio item type that you want to map to
      Clarity
      tasks (for example, feature). The portfolio item type must be at a lower level. For the following integration directions, the portfolio item type has to be contiguous to the portfolio item type that you defined for the Portfolio Item Type Map (Project) field:
      • Clarity
        to Rally
      • Bidirectional
      For the Rally to
      Clarity
      integration direction, the portfolio item type
      does not
      have to be contiguous to the portfolio item type that you defined for the Portfolio Item Type Map (Project) field.
      We recommend that you do not change the value for this field after the initial synchronization. Changing this value can break the connection with Rally.
      If the value for the Portfolio Item Type Map for both project and task is the same, then only one task is created in
      PPM (versión clásica)
      . The task has the same name as the project and all the details from Rally are rolled up to that task during synchronization.
    • Create and Sync Tasks:
      Specifies whether to synchronize the
      PPM (versión clásica)
      tasks with the Rally portfolio items. By default, the option is selected and tasks are synchronized whenever the synchronization job runs.
    • Create Direction:
      Defines the integration direction for synchronizing tasks. Select from the following options:
      • Agile Central to PPM:
        Depending on the Portfolio Item Type mapping, projects that you create in
        PPM (versión clásica)
        are created as corresponding portfolio items in Rally. Child portfolio items that you create in Rally are created as corresponding tasks in
        PPM (versión clásica)
        . If you do not select an integration direction, Rally to
        Clarity
        is used as the default option.
      • PPM to Agile Central:
        Depending on the Portfolio Item Type mapping, projects that you create in
        PPM (versión clásica)
        are reflected as corresponding portfolio items in Rally. When
        Clarity
        tasks are flagged to synchronize, tasks that you create in
        Clarity
        are also created as child portfolio items in Rally.
      • Bidirectional:
        Tasks are synchronized in either direction provided the Synchronize flag is checked at the task level. When configured to synchronize, tasks that you create in
        PPM (versión clásica)
        are synchronized with Rally features. Any features that you create in Rally are synchronized with
        Clarity
        tasks.
      The Create Direction field works with the Synchronize option for tasks in a project that is integrated with Rally. For each task marked as Synchronize, a corresponding portfolio item is created in Rally.
    • Create and Sync Team:
      Specifies whether to synchronize the
      PPM (versión clásica)
      project team with the users assigned to Rally portfolio items. By default, the option is selected and team members are synchronized whenever the synchronization job runs.
    • Team Open for Time Entry:
      Specifies whether the team members that are synchronized from  Rally are open for time entry in
      PPM (versión clásica)
      . Select one of the following options for the integration instance:
      • Yes
        : All the resources that are added to the
        PPM (versión clásica)
        project team from Rally are open for time entry.
      • No
        : All the resources that are added to the
        PPM (versión clásica)
        project team from Rally are not open for time entry.
      • Select
        : The Open attribute value on the Team Object is considered for determining whether the resources that are added to the
        PPM (versión clásica)
        project team from Rally are open for time entry.
    • Default Rally Owner ID:
      Defines the default owner ID to use when a portfolio item (for example, initiative) is created in Rally.
    • Default Rally Project ID:
      Defines the default project ID (the agile team ID) to use when a portfolio item (for example, an initiative) is created in Rally.
  2. Click
    Save
    .
To get the owner or project ID, see Get Rally Integration ID Values
Import the Signed Certificate (On-Premise Only)
The following procedure applies only to on-premise integrations of
PPM (versión clásica)
with Rally SaaS. Customers who install Rally on-premise have the option to generate their own certificate, purchase a certificate from a third party vendor, or use the Rally certificate that is installed by default. On-prem Rally integrations with
PPM (versión clásica)
are not supported.
PPM (versión clásica)
on-premise or SaaS integrations are only supported with Rally SaaS edition.
  1. If you obtain your signed certificate from a third-party vendor, import it to the Rally on-premise console. See Rally Control Panel.
  2. Import the same certificate into the JDK/JRE path for your
    PPM (versión clásica)
    environment:
    1. Navigate to the JDK/JRE file location in the
      bin
      directory on your
      PPM (versión clásica)
      environment.
    2. Go to
      cacerts
      and insert the signed certificate with the following command:
      keytool -import -keystore cacerts -alas <adcert> -file <certificate.cer> -keyalg RSA -trustcacerts -storepass changeit
  3. Restart services for both Rally and
    PPM (versión clásica)
    .
If the Synchronize Rally job fails with handshake SSL errors, verify both systems are using the same certificate. If the job fails due to an invalid workspace ID or configuration value, verify all the integration property values and enter them again. Complete the remaining setup tasks on this page and run the Synchronize Rally job again.
Define the Agile Integration Owner
Define a
PPM (versión clásica)
user as the Agile Integration Owner who can schedule and run the background sync jobs. The jobs sync data between Rally investments, portfolio items, and
PPM (versión clásica)
projects and tasks. The jobs also create investments and other portfolio items in Rally based on
PPM (versión clásica)
projects.
Assign the required access rights to the Agile Integration Owner so they can update the project and associated team and tasks. If the agile summary pages for the project and tasks are secured, assign the secure subpage rights to the Agile Integration Owner.
Follow these steps:
  1. In
    PPM (versión clásica)
    , click
    Administration
    ,
    Project Management
    ,
    Settings
    .
  2. Select the Agile Integration Owner (for example, admin) and save.
  3. Assign the following global access rights to the integration owner:
    • API - Access
    • Projects - Navigate
    • Resource - Navigate
    • Project - Edit Management
      (for specific projects, or for all projects)
  4. Assign the following access rights to the integration owner for investment type integrations:
    • Agile Central Investment - Create
    • Agile Central Investment - Edit All
  5. Assign the following access rights to the integration owner for portfolio item type integrations:
    • Portfolio Item Type - Create
    • Portfolio Item Type - Edit All
    • Portfolio Item Type - View All
    • Portfolio Item Type - XOG Access
  6. Depending on what data you are pulling from Rally to send to
    PPM (versión clásica)
    , assign the following additional rights:
    • Resource - View
      (for specific resources, or for all resources)
    • Resource - Hard Book
      (for specific resources, or for all resources)
Schedule Background Jobs
As the Agile Integration Owner (or the
PPM (versión clásica)
administrator), set up the following jobs to run at scheduled intervals:
  • Create Agile Central Investments:
    Run this job to create investments in Rally using information from the
    Clarity
    project. Use the job for integrating with Rally investments.
  • Synchronize Agile Central:
    Run this job to synchronize
    projects with Rally portfolio items and investments. Use the job for integrating with Rally investments and portfolio items.
The jobs read through all
PPM (versión clásica)
projects that have the Synchronize option selected and an Agile System defined in their agile summary. See Jobs Reference for details.
Configure the Ability to Run the Synchronization Job from Inside a Project
As a project manager, you can run the Synchronize Agile Central job directly from an active project using the Actions menu. With this option, you do not need the access rights to run jobs or view job output. When you click this option from inside an open sync-ready project, you are granted instance-level access rights to the job.
Only the project where you run the job is updated, not all projects. The project ID is included as part of the job name, for example: Synchronize Agile Central (Project2020-1234).
Administrators do not have access to the output of action-menu-driven jobs. The Synchronize Rally menu item is not available by default from the Actions menu of a project. The action is available as part of the Agile add-in items installed for the
Project Properties - General
content item.
Follow these steps:
  1. Click
    Administration
    ,
    Studio
    ,
    Content Add-Ins
    .
    The Content Add-Ins page appears.
  2. Select
    Agile Addin
    and click
    Items
    .
  3. Filter for the Project Properties - General content item and verify that the item is available for installing.
    When you install the Agile add-in, the application displays content items with an
    Upgrade Ready
    status. To protect your configuration, content items in the add-in are not automatically installed.
    image2018-11-20_16-35-8.png
  4. Do one of the following:
    • If you do not have view configurations, select the
      Project Properties - General
      content item and click
      Install
      . The Synchronize Agile Central action becomes available from the main project properties page and subpages for users with edit access to the project.
    • If you have view configurations, manually configure the project properties view in
      PPM (versión clásica)
      Studio to include the Synchronize Rally action in the
      Actions
      menu. See
      Clarity
      Studio Menus and Links
      .
  5. Open the project properties and from the
    Actions
    menu, select
    Synchronize AA
    .
Configure Integration Views
When you install the Agile add-in, some object views are reinstalled to display information in a different way than the default
PPM (versión clásica)
installation. If you previously used
PPM (versión clásica)
Studio to configure the default product views, these configurations do not change. They are not overwritten by new or changed content during the Agile add-in installation. Use the information provided in this section to compare the Agile add-in views to your configurations. You can then decide whether to change your existing product configurations or to apply the new Agile add-in content.
The agile fields listed for the integration, project, and task views in this section are also available in
Clarity
. To view these fields on your project and task pages in
Clarity
, configure the applicable project blueprint details. See
Clarity
: Configure Blueprints for Projects and Investments
for details.
The following table lists the views that are modified for the Integration object in the Agile add-in.
View
Integration Type
Page ID
Display Condition
Rally
Both
agl_integration
Integration Vendor = Rally
Integration Policy
Portfolio Item
agl_pi_policy
Integration Vendor = Rally and Integration Type = Portfolio Item
Portfolio Item Hierarchy
Investment
agl_port_item_type
Integration Vendor = Rally and  Integration Type = Investment
When you apply the add-in, the following configurations become available for the integration views:
5
5
Rally (Portfolio Item or Investment)
The following table lists the fields on the Rally page for both integration types. See
Define the Integration Attributes
in this article for details about the fields.
Section
Field
Corresponding Field in Rally
System of Record
General
Integration Type
N/A
PPM (versión clásica)
Task - Create Defaults
Task Open for Time Entry
N/A
PPM (versión clásica)
Task Cost Type
N/A
PPM (versión clásica)
Task Charge Code
N/A
PPM (versión clásica)
Integration Policy (Portfolio Item)
The following table lists the fields on the Integration Policy page. See
Define the Integration Attributes
in this article for details about the fields.
Section
Field
Corresponding Field in Rally
System of Record
Integration Policy
Portfolio Item Type Map (Project)
N/A
PPM (versión clásica)
Portfolio Item Type Map (Task)
N/A
PPM (versión clásica)
Create and Sync Tasks
N/A
PPM (versión clásica)
Create Direction
N/A
PPM (versión clásica)
Default Agile Central Owner ID
N/A
PPM (versión clásica)
Default Agile Central Project ID
N/A
PPM (versión clásica)
Team - Create Defaults
Create and Sync Team
N/A
PPM (versión clásica)
Team Open for Time Entry
N/A
PPM (versión clásica)
Portfolio Item Hierarchy (Investment)
The following table lists the fields on the Portfolio Item Hierarchy page for the Investment integration type. See
Define the Integration Attributes
in this article for details about the fields.
Field
Corresponding Field in Rally
System of Record
Portfolio Item Type
Portfolio Item
Rally
Ordinal
Ordinal
Rally
Create and Sync Portfolio Items
N/A
PPM (versión clásica)
Project Views
The following table shows the views that are modified for the Project object in the Agile add-in.
View
Integration Type
Page ID
Display Condition
Agile Integration Settings
Both
project_agl_integration_settings
N/A
Agile Summary - Portfolio item Integration
Portfolio Item
agl_integration
Project Integration Type <> investment
Agile Summary - Investment Integration
Investment
agl_inv_integration
Project Integration Type = investment
Properties - General
Both
projectGeneral
Configure the Properties - General view for the Project object to include the Synchronize Agile Central action in the Actions menu. The new action allows users to run the Synchronize Agile Central job at the project instance level.
When you apply the add-in, the following configurations become available for the project views:
Project Agile Integration Settings (Portfolio Item or Investment)
The following table lists the fields on the Project Properties Main - Settings page for both integration types. See Synchronize a Project with Rally Portfolio Items for details about the fields.
Section
Field
Corresponding Field in Rally
Agile Integration
Synchronize
N/A
Create and Sync Stories
N/A
Agile System
N/A
Integration Type
N/A
Project Agile Summary - Portfolio item Integration
The following table lists the fields on the Project Agile Summary page for the Portfolio Item integration type.
Section
Field
Corresponding Field in Rally
System of Record
Notes
General
Portfolio Item ID
ID
Rally
Agile State
State
Rally
Agile Preliminary Estimate
Preliminary Estimate
Rally
Planning
Agile Investment Category
Investment Category
Rally
The attribute is available to all portfolio items in the portfolio hierarchy. You can associate each portfolio item with only one investment category.
Agile Value Score
Risk Score
Rally
Agile Risk Score
Value Score
Rally
WSJF Score (SAFe scoring attribute)
WSJF Score
Rally
Schedule
Agile Planned Start
Planned Start Date
Rally
Agile Planned Finish
Planned End Date
Rally
Agile Release
Release
Rally
Agile Actual Start
Actual Start Date
Rally
Agile Actual Finish
Actual End Date
Rally
Agile Milestones
Milestone
Rally
Story Metrics
Estimated Story Points
Total Story Points
Rally
Accepted Story Points
Accepted Leaf Story Points
Rally
% Done by Agile Plan Estimate
% Done by Plan Estimate
Rally
Estimated User Stories
Total User Stories
Rally
Accepted User Stories
Accepted Leaf Story Estimate
Rally
% Done by Story Count
% Done By Story Count
Rally
Sync Job Information
Last Agile Sync Date
N/A
PPM (versión clásica)
See
Review Integration Status for Synchronized Projects
in this article for details about this field.
Last Agile Sync Status
N/A
PPM (versión clásica)
See
Review Integration Status for Synchronized Projects
in this article for details about this field.
Project Agile Summary - Investment Integration
The following table lists the fields on the Project Agile Summary page for the Investment integration type. See
Synchronize a
Clarity
Project with Rally Investments
in this article for details about the fields.
Section
Field
Corresponding Field in Rally
System of Record
Rally Investment
Create Rally Investment
N/A
PPM (versión clásica)
Last Agile Investment Created Date
N/A
PPM (versión clásica)
Last Agile Investment Status
N/A
PPM (versión clásica)
Rally Investments
N/A
PPM (versión clásica)
Sync Job Information
Last Agile Sync Date
N/A
PPM (versión clásica)
Last Agile Sync Status
N/A
PPM (versión clásica)
Task Views
The following table shows the views that are modified for the Task object in the Agile add-in.
View
Integration Type
Page ID
Display Condition
Task Agile Summary
Portfolio Item
agl_integration
Task Ordinal = null and Task Story ID = null
Task Agile Summary
Investment
agl_inv_integration
Task Ordinal > 0 and Task Story ID = null
Task Agile Summary
Investment
agl_inv_integrationLowest
Task Ordinal = 0 and Task Story ID = null
Task Agile Summary
Both
agl_integrationStory
Task Story ID IS NOT null
When you apply the add-in, the following configurations become available for the task views:
Task Agile Summary (Portfolio Item Integration)
The Agile Summary page is organized into the following sections:
    • Agile
    • Planning
    • Schedule
    • Story Metrics
The following table lists the fields in the
Agile
section.
Field
Corresponding Field in Rally
System of Record
Notes
Synchronize
N/A
PPM (versión clásica)
When the checkbox is selected, the
PPM (versión clásica)
task is created in Rally as a portfolio item. This behavior occurs when tasks are configured to synchronize in the
Clarity
-to-Rally direction or the bidirectional mode (but not when tasks are synchronized in the Rally-to-
Clarity
direction).
Portfolio Item ID
ID
Rally
Parent Portfolio Item ID
The ID of the parent as displayed in the hierarchy
Rally
Agile State
State
Rally
Agile Preliminary Estimate
Preliminary Estimate
Rally
The following table lists the fields in the
Planning
section.
Field
Corresponding Field in Rally
System of Record
Notes
Agile Investment Category
Investment Category
Rally
A budget or investment area that a portfolio item supports. The attribute is available to all portfolio items in the portfolio hierarchy. You can associate each portfolio item with only one investment category.
Agile Value Score
Value Score
Rally
Agile Risk Score
Risk Score
Rally
WSJF Score (SAFe scoring attribute)
WSJF Score
Rally
The following table lists the field in the
Schedule
section.
Field
Corresponding Field in Rally
System of Record
Notes
Agile Planned Start
Planned Start Date
Rally
Agile Planned Finish
Planned End Date
Rally
Agile Release
Release
Rally
The attribute is available only to the feature portfolio item. You can associate each portfolio item (feature) with only one release.
Agile Actual Start
Actual Start Date
Rally
Agile Actual Finish
Actual End Date
Rally
Agile Milestones
Milestones
Rally
The attribute is available to all portfolio items in the portfolio hierarchy. You can associate each portfolio item with multiple milestones.
The following table lists the field in the
Story Metrics
section.
Field
Corresponding Field in Rally
System of Record
Estimated Story Points
Available with Rally API. The value is dynamically calculated by Rally based on user story status.
Rally
Accepted Story Points
Available with Rally API. The value is dynamically calculated by Rally based on user story status.
Rally
% Done By Agile Plan Estimate
% Done By Plan Estimate
Rally
Estimated User Stories
Available with Rally API. The value is dynamically calculated by Rally based on user story status.
Rally
Accepted User Stories
Available with Rally API. The value is dynamically calculated by Rally based on user story status.
Rally
% Done by Story Count
% Done By Story Count
Rally
Task Agile Summary (Investment)
Depending on the portfolio item hierarchy level (theme, epic, initiative, or feature), the corresponding Agile Summary page appears listing the relevant sections and fields.
The following table lists the fields on the Agile Summary page for a portfolio item.
Portfolio Item Hierarchy Level
Section
Field
Corresponding Field in Rally
System of Record
All (Theme, Epic, Initiative, Feature)
General
Portfolio Item ID
ID
Rally
Portfolio Item Type
Portfolio Item
Rally
Parent Portfolio Item ID
Parent ID
Rally
Parent Portfolio Item Type
Type
Rally
Rally Investments
Name
Rally
Agile State
State
Rally
Agile Preliminary Estimate
Preliminary Estimate
Rally
All (Theme, Epic, Initiative, Feature)
Planning
Agile Investment Category
Investment Category
Rally
Agile Value Score
Value Score
Rally
Agile Risk Score
Risk Score
Rally
WSJF Score (SAFe scoring attribute)
WSJF Score
Rally
All (Theme, Epic, Initiative, Feature)
Schedule
Agile Planned Start
Planned Start Date
Rally
Agile Planned Finish
Planned End Date
Rally
Agile Milestones
Milestones
Rally
Feature
Schedule
Agile Actual Start
Actual Start
Rally
Agile Actual Finish
Actual Finish
Rally
Agile Release
Release
Rally
Feature
Story Metrics
Estimated Story Points
Available with Rally API. The value is dynamically calculated by Rally based on user story status.
Rally
Accepted Story Points
Available with Rally API. The value is dynamically calculated by Rally based on user story status.
Rally
% Done By Agile Plan Estimate
Percent Done By Story Plan Estimate
Rally
Estimated User Stories
Available with Rally API. The value is dynamically calculated by Rally based on user story status.
Rally
Accepted User Stories
Available with Rally API. The value is dynamically calculated by Rally based on user story status.
Rally
% Done By Story Count
Percent Done by Story Count
Rally
Task Agile Summary (Portfolio Item or Investment)
The following table lists the fields on the Agile Summary page for a user story:
Section
Field
Corresponding Field in Rally
User Story/Feature/Both
System of Record
Notes
Agile
Story ID
ID (Story)
Story
Rally
Parent Story ID
ID (Story)
Story
Rally
Portfolio Item ID
ID
Both
Rally
Portfolio Item Type
Portfolio Item
Both
Rally
Schedule
Agile State
State
Both
Rally
Agile Release
Release
Both
Rally
Agile Iteration
Iteration
Story
Rally
Agile Status
Status
Story
Rally
The status can be ready (green), blocked (red), or none (gray)
Agile Milestones
Milestones
Both
Rally
Story Metrics
Estimated Story Points
Total Story Points
Both
Rally
Configure Integration Details in Rally
Set Up An Rally API Key
An API key is similar to a password and should be protected. Do not share API keys, store them in source code, or send them over insecure channels. An API key is useful for simple interactions with the Rally API, such as a connector that is not a web application. If you believe an API key has been compromised, either reset it or delete it.
  1. Click
    Create New API Key.
  2. Enter a
    Description
    .
  3. Select the
    Full Access
    checkbox and click
    Create
    .
  4. Retrieve the API Key found under My Keys.
Get the Integration Instance Workspace ID
This value defines the integration instance for the connection from
Clarity
to Rally. For example, this value might represent the Rally workspace ID (this value would be the highest level).
  1. Select
    Workspace
    under
    Object Model
    on the left side.
    image2018-12-4_13-0-47.png
  2. Select the
    Fetch full objects
    and
    Beautified JSON output
    checkboxes.
  3. Click
    Query
    .
  4. In the new window, retrieve the
    Object ID
    .
    image2018-12-4_13-10-25.png
Get the Integration Instance Project ID
The steps are similar to the steps above for a workspace ID.
  1. Search Rally for the parent project name that you want to use with the integration.
    image2018-12-4_13-17-57.png
  2. Select
    Project
    under Object Model on the left side.
  3. Select the
    Fetch full objects
    and
    Beautified JSON output
    checkboxes.
  4. Click
    Query
    .
  5. In the new window, search using your browser find on page feature for the Project name, for example, ACPPM-IntegrationProject1.
  6. Retrieve the Project ID:
    image2018-12-4_13-35-15.png
  7. Within the Project, scroll down to the section that contains
    _type: User
    and retrieve the Owner ID (refObjectUUID):
    image2018-12-4_13-36-25.png
Associate a
PPM (versión clásica)
Project with a Rally Investment (Not Supported)
The following behavior is not supported. Because users might be able to see these new options (as SaaS products,
PPM (versión clásica)
and Rally often roll out new features), they might attempt to perform these steps in Rally; however, the
Clarity
project cannot show the new relationship.
  1. Log in to Rally.
  2. From the
    Portfolio
    menu, select the Investments page.
  3. On the Investments summary page, select an investment.
  4. On the investment detail page, click the … (actions) menu and select
    Connect
    Clarity
    Project
    .
  5. Enter your login credentials associated with your
    Clarity
    instance.
  6. Select a
    Clarity
    project from the project picker and click
    Save
    .
    image2018-12-4_12-49-57.png
  7. Your
    Clarity
    project information appears on the investment detail page:
    image2019-3-25_12-17-12.png
Rally might show new custom fields to display
Clarity
project details inside Rally investments. This functionality is still pre-beta. Those fields exist; however,
Clarity
does not populate them with data. A future release is expected to resolve this. Currently, the only supported place for associating
Clarity
projects with Rally investments is from inside
PPM (versión clásica)
.
Synchronize a
Clarity
Project with Rally Investments
The business stakeholders approve a project to fund a set of features that the product development team can execute. The PMO either creates or updates an existing project in
PPM (versión clásica)
, defines the budget, and links it to the Rally system.
Follow these steps
:
  1. Click
    Home
    ,
    Portfolio Management
    ,
    Projects
    .
  2. Open the project that you want to synchronize with Rally.
  3. Click
    Properties
    ,
    Settings
    .
  4. In the
    Agile
    Integration
    section, complete the following information and save:
    • Select the
      Synchronize
      checkbox to link the
      PPM (versión clásica)
      project to Rally investments.
    • (Optional) Select the
      Create and Sync Stories
      checkbox to bring over user stories from Rally into
      PPM (versión clásica)
      for time tracking purposes.
    • In
      Agile System
      , select the investment integration that the system administrator has configured. If you do not select an agile system, the project is not synchronized.
    • In
      Investment Type
      , select
      Investment
      . The Investment option becomes available only after you select the agile system.
      image2018-11-21_13-41-21.png
      If you select an agile system but do not select the integration type, the synchronize job sets the correct integration type based on the selected agile system. The attribute determines what the Agile Summary page is displayed for the project. (In the screenshot above, note that you can also use blueprints in the Modern UX to configure these project settings.)
  5. Click
    Properties
    ,
    Agile Summary.
    In the
    Rally Investment
    Agile Central section, browse and select the Rally investments that you want to synchronize with the
    PPM (versión clásica)
    project. Only the Rally investments that were created in
    Clarity
    and not already associated with another
    Clarity
    project appear.
  6. As another option, you can also initiate the creation of a Rally investment in
    Clarity
    as follows:
    1. In
      Create Agile Central Investment,
      enter a name for the Rally investment.
    2. Run the Create Rally Investments job. When the job executes successfully, the investment gets created in Rally with the
      Clarity
      project start and end dates.
      Clarity
      updates the following fields:
      • The Create Rally Investment field is cleared.
      • The Agile Central Investments field shows the name of the Rally investment that was created and associated with the project.
      • Last Agile Investment Created Date. The field shows the date when the last Rally investment was created.
      • Last Agile Investment Status. The field shows a message indicating that the Rally investment was successfully created.
      The new investment is stored in the Agile Central Investment master object in
      PPM (versión clásica)
      Studio. Do not edit this master object in
      PPM (versión clásica)
      since the system of record for the data is Rally. Rally investment data only flows from Rally to
      Clarity
      . You can view the investment instances created in
      Clarity
      under Home, Custom Objects, Agile Central Investments.
    3. In Rally, associate your new Rally investment to portfolio items. You can only associate those portfolio items that are at the lowest level in the portfolio item hierarchy.
  7. In
    Clarity
    , run the Synchronize Rally job to bring in the relevant Rally investment portfolio item hierarchy into
    PPM (versión clásica)
    as tasks.
Synchronize a
PPM (versión clásica)
Project with Rally Portfolio Items
After the integration is configured, the project manager can synchronize projects with Rally. By default, the synchronization allows initiative and feature status information from Rally to flow back to the
PPM (versión clásica)
projects and tasks. The project manager has visibility into the work status information in Rally.
To learn how the Synchronize Rally job updates
PPM (versión clásica)
and Rally for each integration direction, see Jobs Reference.
Rally to
Clarity
Direction
Follow these steps
:
  1. Click
    Home
    ,
    Portfolio Management
    ,
    Projects
    .
  2. Open the project that you want to synchronize with Rally.
  3. Click
    Properties
    ,
    Settings
    .
  4. In the
    Agile  Integration
    section complete the following information:
    • Select the
      Synchronize
      checkbox to link the
      PPM (versión clásica)
      project to Rally initiatives or features.
    • (Optional) Select the
      Create and Sync Stories
      checkbox to bring over user stories from Rally into
      PPM (versión clásica)
      for time tracking purposes.
    • In
      Agile System
      , select the portfolio item integration that the system administrator has configured. If you do not select an agile system, the project is not synchronized.
    • In
      Integration Type
      , select Portfolio Item. The Portfolio Item option becomes available only after you select an agile system.
      If you select an agile system but do not select the integration type, the synchronize job sets the correct integration type based on the selected agile system. The attribute determines what Agile Summary page is displayed for the project.
In the Rally to
Clarity
integration direction, the Synchronize Rally job ignores the Synchronize attribute value on tasks. The job does not create portfolio items in Rally from
PPM (versión clásica)
task
Clarity
to Rally Direction
Follow these steps:
  1. Click
    Home
    ,
    Portfolio Management
    ,
    Projects
    .
  2. Open the project that you want to synchronize with Rally.
  3. Click
    Properties, Settings
    .
  4. In the
    Agile Integration
    section complete the following information:
    • Select the
      Synchronize
      checkbox to link the
      PPM (versión clásica)
      project to Rally initiatives or features.
    • (Optional) Select the
      Create and Sync Stories
      checkbox to bring over user stories from Rally into
      PPM (versión clásica)
      for time tracking purposes.
    • In
      Agile System
      , select the portfolio item integration that the system administrator has configured. If you do not select an agile system, the project is not synchronized.
    • In
      Integration Type
      , select the type of integration that the system administrator has configured (Portfolio Item, in this example). The options become available only after you select an agile system.
      If you select an agile system but do not select the integration type, the synchronize job sets the correct integration type based on the selected agile system.
  5. Navigate to Tasks.
  6. For each task, you want to synchronize, click task properties and select Agile Summary.
  7. Select the
    Synchronize
    checkbox.
Bidirectional Synchronization
In bidirectional integrations, features (and user stories if configured in the project) from Rally are brought in as tasks and subtasks in
PPM (versión clásica)
. Tasks from
PPM (versión clásica)
are pushed to Rally as portfolio items.
In
PPM (versión clásica)
, select the
Synchronize
checkbox for projects and tasks that you want to synchronize with Rally.  To synchronize user stories with tasks, select the
Create and Sync Stories
checkbox at the project level.
The following diagram shows how the Synchronize Rally job updates projects with the latest status details from Rally in Portfolio Item type integrations. In all configured task synchronization directions (Rally-to-
Clarity
,
Clarity
-to-Rally, or bidirectional) the behavior is the same.
The image shows how the Synchronize Agile Central job updates
Clarity
projects with status details from Rally
The image shows how the Synchronize Rally job updates Clarity projects with status details from Rally
Synchronize Tasks in Portfolio Item Integrations
The following diagram shows how the Synchronize Agile Central job updates
PPM (versión clásica)
tasks with the latest status from Rally in all integration directions:
The image shows how the Synchronize Rally job updates
Clarity
tasks with status details from Rally
The image shows how the Synchronize Rally job updates Clarity tasks with status details from Rally
The
PPM (versión clásica)
task start and finish dates are populated based on the actual start and end dates of the corresponding Rally portfolio item.
If the actual start and end dates of the Rally portfolio item are not defined, the
Clarity
task start and finish dates match the planned start and end dates of the portfolio item. If both the actual and planned dates are not defined for the portfolio item, the project start and finish dates are used to define the
PPM (versión clásica)
task start and finish dates.
Synchronize Rally User Stories to
PPM (versión clásica)
Tasks
You can synchronize Rally user stories with tasks in
PPM (versión clásica)
to reflect the work progress. With user stories available as tasks in
PPM (versión clásica)
, you can assign team members to the tasks and have them report time against these tasks. Select the
Create and Sync Stories
checkbox on the project Settings page to bring in user stories to
PPM (versión clásica)
as tasks.
If the parent task has assignments, the story tasks show at the same level as the parent task (not as subtasks) in
PPM (versión clásica)
. To synchronize user stories to tasks, map the lowest-level item in the Rally portfolio items hierarchy to a
Clarity
task.
The following rules apply to the user story tasks:
  • The user story dates are used as the task start and finish date.
  • The user story dates come from the parent portfolio item dates.
  • If the user stories have child stories, they are also brought in to
    PPM (versión clásica)
    as tasks at the same level as the parent stories.
See Jobs Reference for details that explain how the Synchronize Agile Central job synchronizes user stories with tasks for each integration direction.
Synchronize Teams in Portfolio Item Integrations
If you select the Create and Sync Team option for the portfolio item integration type, users (or collaborators) who are assigned to initiatives, features, and all child components of features are brought over to
PPM (versión clásica)
when the Synchronize Agile Central job runs.
  • If the Rally users already exist as
    PPM (versión clásica)
    resources, they show up directly on the project team staff page.
  • If the Rally users do not already exist in
    PPM (versión clásica)
    as resources, they appear listed on the Missing Resources portlet.
As an administrator, you can add these users as
PPM (versión clásica)
resources and run the Synchronize Agile Central job to make them appear on the project team staff page. Users with the same first and last names but different email IDs are listed in the Possible Matching Resources column on the Missing Resources portlet. The administrator can either create new resources for these matching resources or use the existing resources by modifying the email ID. All changes to teams are reflected in
PPM (versión clásica)
when the Synchronize Agile Central job runs.
The Missing Resources portlet does not appear by default on any application page. You can configure the
Overview: General
page or any other page to add the Missing Resources portlet using the Manage my Tabs option. See Personalize
Clarity
.
Once the Rally resources are synchronized with the
PPM (versión clásica)
project team, they are not removed from
PPM (versión clásica)
, even if the corresponding resources are removed from the corresponding Rally portfolio items or from Rally.
Similarly, once the Rally features are synchronized with the
Clarity
project task, they are not removed from
PPM (versión clásica)
, even if the corresponding features are removed from the corresponding Rally portfolio items.
You are in the
Synchronize a
Clarity
Project with Rally Portfolio Items
section. The documentation in this section applies only to integrations with portfolio items.
The following diagram shows how the Synchronize Rally job updates the
PPM (versión clásica)
project team with the latest user details from Rally in portfolio item integrations in any direction:
The image shows how the Synchronize Rally job updates
Clarity
project teams with status details from Rally
The image shows how the Synchronize Rally job updates Clarity project teams with status details from Rally
If you import a linked
PPM (versión clásica)
project using XOG, the project remains linked to the Rally portfolio item. To unlink the project from Rally, clear the Synchronize checkbox for the
Clarity
project.
Review Integration Status for Synchronized Projects
To verify that data is successfully transferring to Rally and back to
PPM (versión clásica)
, review the Synchronize Agile Central  job details and the
PPM (versión clásica)
Background (bg) services log file. For more information about how to access the bg services log file, contact your system administrator.
Follow these steps
:
  1. Click
    Home
    ,
    Portfolio Management
    ,
    Projects
    .
  2. Open an integrated project and select
    Properties
    ,
    Agile Summary
    .
  3. Review the following information:
    • Last Agile Sync Date:
      Displays the last time the Rally portfolio items were synchronized with the
      PPM (versión clásica)
      project.
    • Last Agile Sync Status:
      Displays the status of the Sync job as successful or failed. Even if the job status is successful, we recommend that you check the job logs to see if there are any warnings.
Troubleshooting Common Agile Integration Issues
Problem
: Unsuccessful integration can indicate one or more of the following issues:
  • The Rally connection information is incorrectly defined in the
    PPM (versión clásica)
    Integration settings under Administration, General Settings.
  • The Agile Integration Owner is not set up as a dedicated resource for updating integrated
    PPM (versión clásica)
    projects and tasks.
  • The REST API Status is disabled. Verify that the REST API Status appears Enabled on the System Options page under Administration. Search
    REST APIs
    for more information.
  • The Rally server is down.
Solution
: Try integrating again after entering the correct values or completing the setup, and running the Synchronize Agile Central job. You can also review the project integration status.
Problem
: Sometimes an integration error happens because a linked portfolio item (for example, an initiative) is deleted in Rally.
  • In this case, an error message appears when you run the Synchronize Agile Central job.
  • In the
    Clarity
    project, the Synchronize checkbox gets unchecked and the sync status indicates a failure in the synchronization.
Solution
: Relink the project to a new Rally portfolio item to renew the connection.
Assuming you link
Clarity
projects to Rally initiatives and
Clarity
tasks to Rally features, the following behavior is normal. When a Rally feature is moved to a different initiative, the corresponding task in the
Clarity
project is not deleted. However, the task is no longer synchronized with Rally. A new task is created in the project that now corresponds to the Rally initiative where the feature moved. The new task is created only if the project is enabled to synchronize with Rally. During synchronization, this new task is updated from Rally. The old task remains but never gets updated.