Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Product Lifecycle and Platform Matrix
The Supported Platform Matrix outlines the product releases with their supported client-side and server-side information, including supported operating systems, browser, third party plugins, product integrations, character sets, and upgrade paths. To navigate to this page:
CMS-XML Agile 2010 R2 Hot Fix 1 Release
Agile 2010 R2 Hot Fix 1 Release
CMS-XML Release ID isn't set for tasks created from Taskboard
Release ID isn't set for tasks created from Taskboard
CMS-XML Import: Story is put in wrong folder when the Product/Release name matches Team/Sprint name
Import: Story is put in wrong folder when the Product/ Release name matches Team/Sprint name
CMS-XML Agile On Demand Supported Platform Matrix
The attached file is the Agile on-demand platform matrix. This document outlines the supported client-side platform information, including supported operating systems, browsers, third party plug-ins, Serena product integrations, and character sets.
CMS-XML How does the Burndown Chart calculate its values?
The y-axis of the chart represents the remaining Estimated Work. The x-axis is the number of days in the release cycle (when looking at the Release Burndown) or the sprint cycle (when looking at the Sprint Burndown). The number of days are determined by the Start Date and End Date of the release/sprint.
CMS-XML Why do the days on my burndown charts seem a lot fewer than the start and end dates would span?
When you look at the burn down charts for releases , sprints etc. the days value on the bottom of the charts might seem to reflect a smaller number than the start and end dates would make it seem.
CMS-XML Drag and drop of multiple stories in an Epic does not always move all of the stories
With all stories selected in an epic, drag them to a release . Notice that only one of them are moved instead of all selected items.
CMS-XML Sprint and Team fields are not cleared out when Work Item is moved out of Sprint
1. Create a Work Item in a linked Agile Release . The Work Item is replicated into the SBM Project
CMS-XML ItemManagement Web service operations do not return User Login IDs
The ItemManagement Web service operations GetWorkItemChangesForTransaction and GetWorkItem return the User's first and last name for Resource type attributes. This prevents the replication of these data type fields to other tools, which use the login ID, including SBM and the Agile Connector.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Overview (demonstration)
This animation describes what you need to know about Dimensions CM to help you get started with your developement tasks.

Additional Assistance

  • Submit a Case Online
  • FAQs