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 Agile Integration to SBM troubleshooting and research findings.
... and later you don't even have to ... ... in SBM it doesn't create an Agile ... ... If there is no item type selected ... IDM item then no item will create ... because that type isn't mapped in the ... ... system but why doesn't the SBM Title or Agile Name field update? ... of the Agile Name field. ... the code and can't be changed. ... in SBM the name of the Agile ... the SBM ticket name at the beginning ... ... configurable to it doesn't have the SBM ID in the name ? ... a hard coded naming convention built into ...
CMS-XML Pie chart gives error "Input string was not in a correct format"
Columns = Name , Description, QA Owner, Dev Owner, Estimated Effort ... The Chart will return the error "Failed to render the chart: Input string was not in a correct format" This problem only happens if you use the Organize feature and specify a Resource attribute.
CMS-XML When trying to create or delete a work item you get Backlog Name (xxx) has been modified since last retrieval and item won't create or delete.
When trying to create or delete a work item you get Backlog Name (xxx) has been modified since last retrieval and item won't create or delete.
CMS-XML "Name" field and "Description" fields are not available on the Feature work item
In View Designer, neither the Name field nor the Description field are listed in the Attributes list. In the Types Setup tab and the Work Types sub-tab, neither Name nor Description are listed as available fields for the Feature work item.
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.
CMS-XML Inline editor does not save changes between sessions
4. Double click on Development Owner value for some task or user story 5. Enter some value (developer's name ) 6. Exit in-line edit mode
CMS-XML Agile: The record being edited is not selected by default following changes
There are no rows selected in the grid at the moment. Click on the name of any item to open it's Edit popup dialog. The item you have selected is highlighted in the grid on behind the dialog.
CMS-XML Default values are not set for imported data
Expect: If nothing is specified for a list column, apply the default value on Import. Impact/Result:
CMS-XML Work Item attributes are not updated automatically after edit
2. Choose Backlog for selected item 3. Create new story (task,goal story, defect or feature) 4.Click on it in backlog, in opened dialog changed the name 5. Observe backlog Actual Result: Name is not updated. Need to refresh manually page. Expected Result: Name should be updated automatically
CMS-XML Import: Story is put in wrong folder when the Product/Release name matches Team/Sprint name
3. After the import, the story will be in the Sales Dashboard Product and Interim Release. It will NOT be in the Team or Sprint.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs