Skip to Main Content
Cloud Platform

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to for resolution.

For more information about IBM's Ideas program visit

Status Not under consideration
Workspace UrbanCode
Categories Release
Created by Guest
Created on Feb 7, 2017

RTC Integration - need changes to sync with UCR

We currently have production and project defects (work items) coming into UCR via RTC integration. We have an issue in the case of a defect changing Application Change Type from a Project to a Production defect in RTC, it shows up as duplicate in UCR. It does not delete the Project one and adds the Production one, therefore showing it twice. This is causing confusion as well as extraneous data in UCR. The other scenario is if a defect or change is pulled out of a release (target release becomes unassigned in RTC), it is not removed from UCR. This is also causing confusion. The data in UCR should reflect what is actually in RTC. This problem will be severely compounded when we start integrating all of our story cards from RTC to UCR.

Idea priority High
RFE ID 100639
RFE Product UrbanCode Release
  • Admin
    Osman Burucu
    Jul 4, 2022

    Thank You for entering and providing information to this RFE. Due the age and changes in the products over time additional functionality was introduced which could help to adress this RFE, this RFE will be closed.

    IBM UrbanCode Release is EOS now, please have a look at IBM UrbanCode Velocity

    Please provide a new RFE based on the latest versions if needed

  • Guest
    Apr 21, 2021

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.

  • Guest
    Aug 10, 2017

    Additional Note - forgot to mention that we have updated the integration to include Unassigned, but that has not changed anything - Unassigned releases will continue to display in the original release that was selected for the work item.

  • Guest
    Aug 10, 2017

    Hi, I work on Kelly's team, Kelly has moved to a new position here so I thought I'd try to add more information about this one. We currently use the UCR integration with RTC where work items that are scheduled for a release are pulled into UCR. Our problem is that if a work item is changed from "release x" to "unassigned" in RTC, UCR does not pull the work item from the release.

    Note that if the release is changed from "Release X" to "Release Y" in RTC, UCR does show the update appropriately. Is there some way to make UCR remove the work item from the release if it is simply unscheduled? I was thinking that we needed an "unassigned" release in UCR until this is fixed, but not sure if that would work.

  • Guest
    Aug 2, 2017

    This request lacks sufficient information for us to evaluate it. It might not be considered further until it has been revised and clarified. Rather than using multiple queries, we would recommend using a single, broader query that captures all of the work items that are currently imported. Would this approach be feasible?