May Sprint 1

Prev Next

User Profile Page Revamp

Applicable to

All Interfaces

User profile page is getting a makeover. The user profile page will now open into a display view with a dedicated button to edit profile information. These changes are aimed at streamlining the usability of TeamTracks.  

New user profile page

 Default Profile Image

The first step in making TeamTracks personal is having your own smiling image looking at you. We are starting with having the name initials as default.

Old profile Image
New default image with initials

Better Change Password workflow

The change password workflow has been revamped. The user now has to enter the current password to authenticate and has to reenter the new password.

A show password button is also available if you need to see the entered password as plaintext.

Password for any user can be reset by the Admin anytime from the Admin Interface under Team Members without the current password.

password reset screen from admin


Lookup fields gets more juice

Applicable to

Lookup fields | ChangeField Action

Lookup Field now has more juice than ever. You can use more than one key, i.e, "Search by Value" and "Search by Field" combinations, to find your data. 

In the example scenario below, the configuration is looking up the price of an object using 3 fields, Product Family, Product Model and Product Name.

The underlying track with the pricing data is below for context.

The multiple keys generate a condition block joined by and operators. In SQL this looks similar to the below code block.

SELECT Price FROM *table_name*
WHERE (['<Product Family ID>'] = '<Product Family>' AND
['<Product Model ID>'] = '<Product Model>' AND 
['<Product Name ID>'] = '<Product Name>') 
OFFSET 0 LIMIT 1

New Action - ChangeFieldInAnotherTrack

Applicable to

Admin Interface | Actions

A new action has been introduced enabling the admin to change a field in another track in the system. The new action, called "ChangeFieldInAnotherTrack" can set the value of a field of an object in another track using a literal value specified in the action or from a field in the object that triggers the action.



New configuration option - Hide from Navigation

Applicable to

List Views | Charts | Reports | Dashboards

A new control has been introduced to Lists, Reports, Dashboards and Charts. Admins can now hide these objects from appearing in the left side panel in the agent interface.

This setting is especially useful when creating these objects to be used only in dashboards, keeping the navigation pane de cluttered.


Extending Clone 

Applicable to

Charts | Reports | Dashboards | Filters | Documents

A lot of users have requested the clone functionality be extended and we have listened. You can now clone Charts, Reports, Dashboards, Filters and Documents in addition to views and track-types. All of the configuration of the source object is cloned except the role assignments.

Happy cloning people.


Extending User groups

Applicable to

Charts | Reports | Dashboards | Documents

A lot of users have requested the User Groups option to be made available in commonly used objects. User groups are now available on Charts, Reports, Dashboards, and Documents in addition to views. This helps the Admin assign an object to multiple user groups (team and client roles) from the object itself, improving usability. With clone and user groups now available on all relevant objects, adding new reports and charts are a breeze.


Displaying data values in charts

Applicable to

Charts

Data values can now be displayed persistently in charts. Previously these were visible only on mouse over. 

Count values can be enabled using the "Show Count" check box in chart configuration.

Charts can now be downloaded as an image from TeamTracks to be used in a PowerPoint or report with at a glance data.

Other Enhancements and Bug fixes

  • More fixes to the "Go Back" button.
  • When a relationship object is added/deleted from a parent object, the action is now recorded in the parent object history.
  • Fixed a bug where formula fields were not recalculated when a relationship object is deleted.
  • Charts using two fields can now be downloaded as an image.