|
|
|
|
|
|
Release: TeamHeadquarters version 5.8
Primary focus: MSXML 6
Version 5.8 of TeamHeadquarters was a technical release in support of Microsoft's new version of their XML parser. The new parser has a variety of performance and stability improvements.
MSXML6 is now required for TeamHeadquarters.
Release: TeamHeadquarters version 5.7
Primary focus: New Product Versions
With version 5.7, we have formalized the most requested variety of our product versions.
This is the full-featured UTM Suite with a comprehensive set of professional services for driving the success of your TeamHeadquarters implementation.
TeamHeadquarters Unified Team Management offers all of the software features, along with all of our Software Development Kits.
TeamSuite is a departmental solution which includes the TeamHeadquarters Project Management and Help Desk software.
TeamHeadquarters Help Desk is our multi-Queue ticketing and reporting solution.
Microsoft's IE7 browser is supported by this TeamHeadquarters release.
This new report is a listing of ticket activity for a particular user for a selected number of weeks.
When the Email Agent creates or updates tickets in TeamHeadquarters, it can create up to 4 different color shades on those tickets as they are viewed in Queues, Ticket Monitor, or My Tickets.
For newly created tickets.
For tickets updated by an email from the customer of the ticket.
For tickets updated by someone whose email address is on the Notify line of the ticket.
For tickets updated by anyone not listed above.
Release: TeamHeadquarters version 5.6
Primary focus: Project State Sensitivity
With this release, TeamHeadquarters functions differently depending on the State of a Project or Task:
Project Invitation emails are only sent when the project is in an Active state.
My Tasks only shows non-closed tasks from Active Projects.
My Projects only shows Active Projects. Projects in the Due Diligence or Planning states will also be listed here for those listed as Project Manager.
The Resource Allocation Report now shows the breakdown of allocation for each week in separate sections depending on Project State for Active, Due Diligence, and Planning. Allocation for Frozen and Closed Projects is not represented in this report.
Time Sheets now show only non-closed tasks from Active Projects.
The Active Work reports now show only those projects that are in an Active State and non-closed tasks from those projects.
Time Sheet Auto-Populate can now be performed by Day or Days within the week.
The Project's Object Path (i.e. the physical location of the project) is now displayed on the Project Information page. This page is available by clicking the Info link on project menu, or by right-clicking on the project and selecting Properties.
The URL Object now supports link prefixes of:
http://
https://
ftp://
file://
When a Queue is closed, tickets can no longer be created within it.
Release: TeamHeadquarters version 5.5
Primary focus: Ticket Templates and Resource Allocation
Tickets can now be set up or changed using pre-defined templates. This is a work flow feature that saves time, improves accuracy, and reduces the amount of training/documentation needed to run your organization.
Tickets can now be cloned, using a right-click menu option.
Pre-defined tickets can be created in a batch using the Command List function. This is helpful for more complex and repetitive processes.
Ticket assets have been added as an optional section within the ticket.
A catalog of pre-defined assets can be set up by the TeamHeadquarters Administrator, for selection on tickets. Each selected asset can have a dollar value and quantity, allowing for an internal E-commerce capability within TeamHeadquarters.
This feature provides the opportunity to specify deliverables within the ticket, directing fulfillment for such uses as sales orders, internal purchasing, and corporate logo-wear catalogues. Also, this feature can be used to specify asset types for help desk hardware/software issues.
The new default view for Ticket History is a Summary view, showing only Comments along with each Comment's date/time and author. The detailed audit trail history is still available, by selecting Detail.
This button is available on the Ticket edit screen. It allows the user to apply their changes, adding a history line to the ticket, while leaving the ticket open for further editing.
When your customers submit or modify tickets using the TeamHeadquarters Email Agent, those tickets are shown with a green shade in all ticket list views (i.e. Queue, Ticket Monitor, My Tickets, and Task Console View) until the ticket has been modified by a TeamHeadquarters user. This enhancement helps to improve responsiveness by placing focus on recent customer input that is awaiting a response.
On tickets where the entered customer name brings up a result list of only one entry, that Customer is automatically selected and placed in the ticket. Where the selection is wrong, use the 'Clear' button and hit the 'Select' button to refine the search.
A 'what if' scenario from the Task edit page shows the pending result of saving changes to task dates, estimated time on task, or resource assignment.
Click on any resource on the Task edit page and see a Resource Allocation Report covering the period specified by the task's planned date range for those people shown on the task roster.
Also, the Resource Allocation Report now shows a 'Balance' for each user (i.e. the net hours over or under capacity) for the period selected, and a drill-down to the task details contributing to the report.
The Personal Report Menu now lists 3 new reports: My Work Performed, My Work Closed, and My Active Work. These reports show a blend of Project, Task, and Ticket information.
A new menu was added, for Organizational Unit Reports. It offers 3 new reports: Work Performed, Work Closed, and Active Work. These reports show a blend of Project, Task, and Ticket information.
With version 5.0, Ticket edits automatically cause Tasks and Projects to appear in the User's Time Sheet, even if that User is not on the Project or Task Roster. With version 5.5, this feature was further enhanced so that the User is automatically added to the Project Roster, in an Inactive State with their default cost and billing rates, when saving the Time Sheet.
The Project has a new field, for Baseline Planned End Date. This date is included on the Project Summary Report, Management Report, and in the exported data for Portfolio .csv and EntryXML SDK.
Setting the Phase Completion Date in the Project Edit dialog no longer forces the phase to be set as closed. As a result, the phase dates can be used for planning and projection purposes.
Tasks can be set to start before the project start date by using the Start No Earlier Than constraint on the Task edit page. This option allows for a series of tasks to be structured to start before the project by also using task predecessors in conjunction with the Start No Earlier Than constraint. As a result, project management and planning time can be allocated before the Project's formal start date.
There are now fewer confirmation messages when saving and submitting Time Sheets. Also, an option has been added to restrict the Re-Open function to only TeamHeadquarters Administrators.
The Time Sheet Report has been revised to show a more complete breakdown of Billable and Total costs.
A new system-wide option has been introduced, which can be used to allow only TeamHeadquarters Administrators to access to the Billing and Cost rates section of the User Preferences page.
Release: TeamHeadquarters version 5.1.0
Primary focus: Small enhancements
When viewing the expanded details within a Resource Progress Report, the Estimated Time on Task now shows allocated hours as a break-down by person.
Urgency has been added to the filters for Queues and Ticket Monitor.
An additional filter option is now available on Queues, Ticket Monitor, and My Tickets. By clicking Just Mine?, only tickets that have the current user as 'Primary Responsible' will be shown.
For the Task Properties page, the Task % Overrun has been changed from a bar chart to a numeric percentage. When the Actual Time on Task exceeds the Estimated Time on Task, the % Overrun is calculated as:
(Actual Time on Task / Estimated Time on Task) - 100%
TeamHeadquarters will now retain your sizing preferences between the left and right frames in the main interface.
Under each Project in the time sheet, there is an entry line for the Project itself (before the entry lines for tasks are shown). This line is now shaded to provide visual distinction between it and the task lines.
The Project/Task display has been expanded to allow for longer names.
The Ticket List report now shows the ticket State (i.e. Open/Closed) as a column.
Release: TeamHeadquarters version 5.0.9
Primary focus: Small enhancements
Tickets can be edited with a single click
on the 
ticket icon.
Some 
Task names are too
long to display in the 
Time Sheet. Hovering
your mouse over the task name will cause the full name to pop up for display.
Releases: TeamHeadquarters version 5.0.0 - 5.0.8.
Primary focus: The integration of ticket queues into projects.
Project Queues|
|
Projects now contain a project ticket queue, as shown in the tree view. These queues operate the same as other queues, except for the fact that they share a roster with the project itself. |
Tickets can now be related to tasks. This opens up a variety of new options for project management techniques. In particular, it is now possible to build a task structure at a higher level, with tickets under the task to represent the lower levels of work assignments. As a result, the project's task plan can become much easier to maintain than is the case in classic project management techniques.
Tasks can be viewed with their associated tickets, using the task's Console View (Tickets) as shown below in the standard TeamHeadquarters interface as well as via the Gantt.
Time SheetsTime can now be charged to generic 'charge buckets', as defined by the system administrator. If used, these charges can be recorded by any user of the system.
Since tickets can be related to tasks, it is now possible to use the time records from tickets to auto-populate time sheets. The time sheet illustration below shows the project in green (with the ability to charge time directly to the project directly underneath it), the task in yellow, and related tickets in blue (with individual ticket history entries in grey).
ProjectsThe Invite/Manage Members function for projects now includes an Active/Inactive indicator. As a result, members can now be set as Inactive without losing the associated settings for cost/billing rates, etc.
Phases can now be deactivated in the Project Edit function, which prevents those phases from being listed on the Project Summary Report and Management Report.
The Gantt Chart now allows for re-sorting the tasks by:
chronological order
scheduled start
scheduled end
task name
WBS order (as imported from MS Project or as set on in the Task Edit function)
TasksResource assignments can now be divided between multiple resources in unequal percentages.
The Estimated Time on Task and Duration fields can now accept 2 decimal positions. Durations can be as small as 0.01 of a day and Estimates can be as small as 0.01 of an hour.
A new field, WBS, has been added to the task form for Work Breakdown Structure number. This field can be imported and/or edited, and is used for the WBS sort option in the Gantt chart.
Since Tickets can be related to Tasks and Projects, the Queue Reports can be run for those collections.
The Resource Allocation Report now reflects personal and global non-working days as unavailable time, as well as a unique hours per week for each user.
Queues|
|
Ticket history entries can now be set as either Billable or Non-Billable. The Queue Edit function now includes the default setting for this parameter, which is used when editing or creating a ticket. |
TicketsThere are several new ways that make it easier to create tickets:
Right-click on a task and select New Ticket. When
the new ticket is saved, it will be created in that project's queue and related to that task.
Right-click on a project and select New Ticket.
When the
new ticket is saved, it will be created in that project's queue and related to that project.
Use the New
Ticket drop-down at the top of either 
My
Tickets or the 
Ticket
Monitor. When
the new ticket is saved, it will be created in the queue
or project queue that was selected.
Tickets can now be assigned to multiple resources at the same time, with one marked as primary.
There are 4 additional category fields added to the tickets interface. Called Ticket Customizable Fields, their labels and drop-down options can be modified via the System Administration interface. These fields are optional at the system level.
With the addition of multi-responsible tickets and 4 customizable fields (see above), the layout of the ticket screens has changed.
Ticket history lines can be effective-dated while in the ticket edit function. The effective date drives the auto-population of time sheets when tickets have been related to tasks.
All changes to Reason, Initial Description, and Resolution are now captured in the ticket's history and are now accessible through the Text Filter on queues and ticket monitor.
System Administrators can now delete Queues, Tickets, and Contacts (assuming that they have the appropriate security permissions).
There is now a distinct list of TeamHeadquarters Administrators that controls access to system administration functions.
|
|
Version 5 of TeamHeadquarters includes an optional SDK for development of XML Web Services reporting clients with tools such as Microsoft Excel and Microsoft Access. For more information, speak to your Entry Software Account Representative. |
This .pdf document has been revised for version 5.x, and can be accessed here.
