| |
Results |
|
Privileges must be set at the Base Project level for users to add/modify filters to join condition in reports
|
Privileges must be set at the Base Project level for users to add/modify filters to join condition in reports
|
|
|
|
Project not selectable in various locations when moved
|
If you go to the base project in the Application Administrator and create a new project to be used as a container project that other projects will be under and then move a project under that container project , the project that was moved will not be selectable in various locations where you would need to select a specific project . One example is in the Import Data section of the Application Administrator.
|
|
|
|
Vertical scroll bar is missing on IM - Base Active State form when loaded in Internet explorer - IE
|
Steps to reproduce: 1. Submit a new item into Base Project > Incidents 2. See at state "Investigation and "Diagnostics" that the vertical scroll bar is missing.
|
|
|
|
Handling User and Group Selections in New Web-based Administrator
|
Beginning with SBM 10.1, workflow modifications can only be made in SBM Composer. This change requires you to manage selections for User, Multi-User, and Multi-Group fields for projects in Application Administrator. (In past releases, selections for these field types were managed for workflows in System Administrator.)
|
|
|
|
List report based on state field shows same field value multiple times
|
A common State is added in each workflow. In SBM Work Center, create the project listing report by adding search filter, filter by State Expected result
|
|
|
|
If you upgrade from 2009 Rx to 10.1.2.x then the termination rule not visible on escalation at base workflow
|
This is related to but not the same as DEF226836. It seems like some change has been made that partially fixes DEF226836 in that escalations that are not associated with a project now appear at the base workflow level but this new defect occurs. New issue is that when you open the escalation at the base workflow level and look at the terminate rule, you can see it but when you edit there are no conditions shown.
|
|
|
|
Web Admin: In project view, the + (plus) icon expands ALL children under ALL parents
|
ProjectA2.2 2) Open the web admin tool, and click on Projects. 3) On the right side, double click on Base Project .
|
|
|
|
SSM: User roles in the "Incident Tasks" project are not inherited from the "Incident Management" project
|
6. Note the roles that are enabled for Carmen ("Level 1 Tech" is enabled; other roles are disabled) 7. Return to the Base project 8. Select the "Incident Tasks Project"
|
|
|
|
States in sub-projects not shown when creating or modifying a Report
|
In TeamTrack 6.6.1, if you create a report based on a project which is a direct child of the Base Project , values for the State field (when specified in the Search Filter), may not show all the States from child projects . Only States created at that level are displayed. Workaround: Create and Save the Report from the highest level Project (Base Project) with the appropriate State selections.
|
|
|
|
Data from joined table shown as * when join report is saved at sub project level
|
Here is summary of the problem: Base Project ->Sub Project 1 (Table1) ->Sub Project 2 (Table2)
|
|
|
