TeamCompanion 6.0 supports Microsoft Outlook 2016

Now you can use your favorite Team Foundation Server client with the newest version of Microsoft Outlook 2016!

Team Companion In Outlook 2016

Simply fetch TeamCompanion v6.0 compatible with your TFS server from our download page and use it from within Outlook 2016.

Team Companion In Outlook 2016

Please contact our support team in case you run into any issues with Outlook 2016.

TeamCompanion Best Wishes

 

We wish you all the best for the Holiday Season and a prosperous New Year!

TeamCompanion v6.0 Released

TeamCompanion v6.0 supports Team Foundation Server 2015 and Visual Studio Online,  introduces new productivity features and brings changes to the maintenance policy.

Support for Team Foundation Server 2015 and Visual Studio Online

TeamCompanion v6.0 now supports Team Foundation Server 2015 on-premises. In order to connect to this version of TFS you need to install Team Explorer for Microsoft Visual Studio 2013.

Team Projects hosted on Visual Studio Online and Team Foundation Server 2013 and 2012 are supported as in our previous versions.

TeamCompanion- Visual Studio 2015

Custom Coloring of Work Items in Query Result Lists

TeamCompanion v6.0 introduces custom work item coloring in the query result list. Now you can take advantage of powerful grid coloring capabilities to differentiate work items by their type, state, blocked status and additional custom criteria.

For more details, please check the blog post Color Your Work Items with TeamCompanion v6.0.

TeamCompanion - Color Work Items - Sprint Backlog Grid Coloring Options

 

Excel Like Column Level Filtering

TeamCompanion v6.0 features easier Excel like column level filtering while previewing work item query results. Each column in the grid now includes a built in dynamic filter that allows you to quickly filter your view based on values from one or more columns. Advanced filtering options are available as well.

For more details, please check the blog post Easier Filtering in Work Item Query Results.

TeamCompanion - Grid Column Level Filtering - Column Filters

New Maintenance Policy

Starting with TeamCompanion v6.0, yearly maintenance will be charged. A one year support is included with each purchase of TeamCompanion 6.0. If you own one of our previous versions, you will first need to upgrade to TeamCompanion v6.0 and then later extend your maintenance period.

For more details, please check the blog post TeamCompanion is Introducing New Maintenance Policy.

Older Versions Discontinued

You can now download either the newest version v6.0 (where the license includes our maintenance options) or the previous version v5.2 Update 1 (with no support options). Previous versions of TeamCompanion are not available for download any more.

Various Fixes and Improvements

As always, we need to thank you for your feedback. In the newest version we fixed various bugs (e.g. several issues when creating work items from mail; added full support for RTF E-mails) and improved particular features (e.g. several issues in the setup procedure are fixed; installation troubleshooting tools are now bundled with the setup package).

Color Your Work Items with TeamCompanion v6.0

TeamCompanion introduces custom work item coloring in the query result list. Now you can take advantage of powerful grid coloring capabilities to differentiate work items by their type, state, blocked status and additional custom criteria.

Colors are a powerful means of communication. They can help you emphasize important information, group related items, portray time and progress, and identify changes.

TeamCompanion embraces colors and now features powerful grid coloring capabilities to help you differentiate work items by their type, state, blocked status and additional custom criteria.

Once you get familiar with the color palette of your choice, you can quickly get a status update just by taking a glance at the colored query result list. The colors will quickly inform you about work item state changes and blocked items, and draw your attention to the most important information.

How to Customize Grid Coloring

In TeamCompanion v6.0 work item coloring is turned on by default.

Coloring options as well as the color palette can be adjusted on the Project Settings tab in the Options dialog. The Colors tab provides the option to configure colors used for particular work item types, work item states, and to emphasize blocked work items. Click on the Configure colors button to open the Configure colors dialog where you can adjust the color pallete.

For each coloring option you can define following parameters:

  • Foreground Color – defines the text color, 
  • Background Color - defines the background color (use transparent to omit coloring),
  • Full Row – check to apply selected foreground and background colors to the whole row. If unchecked, the foreground and background colors apply just to the Work Item Type, State and Blocked cells respectively (if they are visible in the query result list).

Team Companion -Color Work Items - Coloring Options

The following picture shows a sample colored product backlog query result list.

TeamCompanion - Color Work Items - Product Backlog Grid Coloring

The default coloring settings used in the above grid are shown in the following picture:

  • The work item types Bug and Product Backlog Item use the firebrick and royal blue colors for the background of the Work Item Type cell.
  • The State cell uses yellow, orange and green to mark the Approved, Committed and New states respectively.

TeamCompanion - Color Work Items - Product Backlog Coloring Options

 

The following picture shows a sample colored sprint backlog query result list.

TeamCompanion - Color Work Items - Sprint Backlog Grid Coloring Options

The default coloring settings used in the above grid are shown in the following picture:

  • The work item types Bug, Product Backlog Item and Task use the firebrick, royal blue, and gold colors for the background of the Work Item Type cell.
  • The State cell uses yellow, orange, green and light grey to mark the Approved, Committed, Done, To Do/In Progress states respectively.
  • Blocked items are emphasized on the level of the whole row by the red background color.

TeamCompanion - Color Work Items - Sprint Backlog Coloring Options

 

By combining values for all available coloring options you can adjust the color palette to your particular needs and/or the needs of your development team. The following picture shows a sample sprint backlog query result list where the coloring palette uses slightly lighter colors than those in the default settings. Full rows are highlighted for the Product Backlog and Bug work item types. The In Progress state is also marked differently.

TeamCompanion - Color Work Items - Sprint Backlog Grid Coloring Options - Lighter Palette

 

Note: Coloring is retained in the grid while searching and filtering and while using the newly introduced excel like column level filtering.

Team Companion - Color Work Items - Grid Coloring Retained When Filtering And Searching

How to Define Custom Criteria For Grid Coloring

You can also define your coloring criteria based on custom rules applied to other work item fields.

For example, if you turn off all predefined coloring based on work item types and states and blocked status, and define custom rules based on values of the Assigned To field, you can achieve a view like on the following picture.

TeamCompanion - Color Work Items - Sprint Backlog Grid Coloring - Custom Rules

The custom coloring options for this example are visible on the next picture.

TeamCompanion - Color Work Items - Coloring Options - Custom Rules

 

Grid Coloring in the Agile Project Management Tools

Custom grid coloring is also available in product and iteration backlog lists in the TeamCompanion’s agile project management tool Plan and Prioritize.

TeamCompanion - Color Work Items - Agile Management Tools - Product Backlog List

TeamCompanion - Color Work Items - Agile Management Tools - Sprint Backlog List

 

How to Turn Off Grid Coloring Options

In TeamCompanion v6.0 work tem coloring is turned on by default.

Each coloring option can be switched on or off, allowing you to set up a combination that suits your needs. For example, if you want to emphasize just bugs, you can set up transparent background for all work item types except for Bug, and completely turn off the other two coloring options.

TeamCompanion - Color Work Items - Product Backlog Grid Coloring - Less Coloring Criteria 

If you prefer the “black-and-white” query result list, you can switch to the old standard view by turning off all coloring options and removing any custom formatting rules.

Grid Coloring Options As Project Level Settings

Like all other settings on the Project Settings tab, grid coloring options can be set as a project policy on the level of each team project. Only project administrators can manage project policy settings and they must explicitly save all changes to the policy on the server. In this case, policy settings are automatically distributed to all users after they restart Outlook. If users previously defined any local coloring settings, these will be overwritten with server policy settings without warning. Users without administrative privileges can only preview policy settings.

Start Coloring Your Work Items with TeamCompanion v6.0!

Many studies show that color is the most important visual experience for human beings. When colors are used correctly, they function as a powerful information channel and allow people to notice and learn more. Memory for “colored” information seems to be much better than memory for information presented in black-and-white.

This powerful mechanism is now featured in the newest TeamCompanion version. Simply unleash your creative side, and find the best color combinations for presenting project level information to your development team!

Easier Filtering in Work Item Query Results

TeamCompanion v6.0 brings easier filtering while viewing work item query results. Each column in the grid now includes a built in dynamic filter that allows you to quickly filter your view based on values from one or more columns.

TeamCompanion supports full text search over all work item fields as well as advanced work item field search conditions since its earliest version. The newest version v6.0 introduces dynamic filtering on the level of each column in the work item query results grid.

Excel Like Column Level Filtering

In the right corner of each grid column header there is an arrow button used to access the filter for that particular column. Filter dropdown lists are dynamically populated with unique values from respective columns. The following picture shows filters for 2 columns in a sample sprint backlog query result list.

TeamCompanion - Grid Column Level Filtering - Column Filters

To apply a particular filtering value, click on it in the filter dropdown. The query result list will be filtered based on this value and will show a subset of work items that meet the filter criteria.

The following picture shows how the above sample sprint backlog query result list looks after applying the filter [Work item Type] = ‘Task’. The arrow in the column header has changed the color to black, indicating that a filter is applied on that column. Additionally, a status bar appears at the bottom of the list, displaying the value of the current filter.

TeamCompanion - Grid Column Level Filtering - Filter Per Work Item Type

You can filter by more than one column. Filters are additive, which means that each additional filter is based on the current filter and further reduces the subset of work items displayed in the list.

The following picture shows how our sample sprint backlog query result list looks like after applying two filters: [Work item Type] = ‘Task’ and [Assigned To] = ‘Cameron Skinner’

TeamCompanion - Grid Column Level Filtering - Filter Per Work Item Type And Assigned To

 

The status bar on the bottom of the list displays the value for the current filter. You can access the list of all recently used filters by clicking on the dropdown arrow next to the filter. To apply one of the previous filters, just click on it in this list. To clear the current filter, uncheck the filter checkbox in the status bar. To close the status bar, click on the button x.

TeamCompanion - Grid Column Level Filtering - Recent Filters

Once you have filtered data in the work item query result list, you can either reapply another filter or clear all filters to redisplay all work items originally included in the result of the query you were filtering.

The Reset View action on the Work Item(s)/Query ribbon or in the query’s context menu in Navigation Pane) will remove all filters applied and reset the query to the version previously saved on TFS.

Special, Custom and Advanced Filtering Options

Each column can be filtered by two distinctive predefined values: (Blanks) and (Non blanks). The following picture shows the list after the filter [Remaining Work] is Null has been applied.

TeamCompanion - Grid Column Level Filtering - Filter Per Blanks And Non Blanks 

To create a custom filter for a particular column, click on the value (Custom) in the column’s filter dropdown and set your conditions.

For example, if you want to filter out work items with Remaining Work values between 4 and 10, you can use the filter shown on the following picture.

TeamCompanion - Grid Column Level Filtering - Custom Filter

TeamCompanion - Grid Column Level Filtering - Grid With Custom Filter

If you click on the Edit Filter button that appears right in the status bar on the bottom of the list, the advanced Filter Editor dialog is displayed. There you can combine multiple filtering options using advanced criteria.

TeamCompanion - Grid Column Level Filtering - Advanced Filter

 

Searching in Filtered Lists

When you use the full text search or advanced work item field search conditions to search filtered work items, only work items that are currently displayed are searched; work items that are not displayed are not searched. To search all the data, first clear all filters.

The following picture shows the results of searching by [Assigned To] = ‘Brian Keller’ on the sample sprint backlog list when no filters were previously applied, and when the filter [Work item Type] = ‘Task’ was previously applied on the list.

TeamCompanion - Grid Column Level Filtering - Search Through Filtered List

Dynamic Column Level Filtering Will Enhance Your Productivity

We believe that this new feature will further enhance your productivity on a daily basis.

Dynamic filtering on the level of each column in the work item query results grid will allow you to quickly locate the data you are actually searching for, without the need to manually author filters. If you still need more advanced searches, you can always use the standard and advanced TeamCompanion's searching and filtering capabilities.

TeamCompanion is Introducing New Maintenance Options

Starting with TeamCompanion version 6.0, yearly maintenance will be charged. A one year support is included with each purchase of TeamCompanion 6.0. If you own one of our previous versions, you will first need to upgrade to TeamCompanion v6.0. and then later extend your maintenance period.

Our team has been actively supporting our customers since the first release in 2007 free of charge. However, due to the growth of our support activities and the need to manage several different flavors of Outlook and Team Foundation Server, we are introducing new maintenance options. Starting with TeamCompanion v6.0, active support will be charged.

Customers purchasing TeamCompanion v6.0 will get paid maintenance for the duration of one year.
Customers who purchased their licenses before September 16th, 2015 have two options:

  1. In case you already own licenses for v5.0 or higher, you can update them to the newest license for v6.0 free of charge. This includes paid maintenance until April 1st, 2016. After this date you will need to extend your maintenance period.

  2. In case you already own licenses older than v5.0, you can upgrade them to the newest license by paying the reduced license fee (visit the upgrade page for more information). You will then get paid maintenance for the duration of one year. After that, you will need to extend your maintenance period.

  3. You can continue using your current TeamCompanion versions up to v5.2, however no support will be provided.

In case you do not extend you maintenance period after it has expired, TeamCompanion v6.0 will continue to work, but no support will be provided to you. Additionally, you will neither be able to activate your v.6.0 license again nor upgrade it to any future new version.

Maintenance Extension Procedure

You can initiate the maintenance extension procedure in 3 different ways:

  1. From within TeamCompanion on the Help/License Activation dialog,

    Maintenance Extension Procedure From TeamCompanion

  2. On the TeamCompanion’s Buy Now web page,

    Maintenance Extension Procedure From BuyNow Page
  3. Directly on the Maintenance web page.

    Maintenance Extension Procedure From Maintenance Page

To extend your maintenance period for an additional year first enter your license information and click on the Get license details button. Details about your current licenses will be displayed below on the same page. Next, choose the number of licenses for which you want to extend the maintenance period and proceed with the purchase.

Maintenance Extension Procedure Choose Maintenance Options

After completing the purchase, you will receive your licensing information within 24 hours by e-mail. Please make sure to include a valid e-mail address with your order.

Maintenance Extension Procedure Purchase Maintenance

If you have any further questions related to product licensing, maintenance options, pricing, ordering, or delivery, please feel free to contact our sales representative.

TeamCompanion under your Christmas tree!

All MSDN subscribers can now get TeamCompanion at a special discounted price. You can get 20% off single licenses and even more when buying more!

TeamCompanion does not care about Black Friday or Cyber Monday. We joined the
Microsoft Connect(); conference series of announcements with a limited time offer valid for the entire upcoming holiday season and beyond! Our special offer is exclusively available to all active MSDN subscribers through the MSDN Special offers page thanks to our Visual Studio Partner status.

Do not miss this great opportunity to empower your entire team with our first class Microsoft Visual Studio Online and Team Foundation Server client embedded into Microsoft Office Outlook, which will help you bridge the gap between your stakeholders and your development team in the most efficient way.

We wish you all the best for the Holiday Season and a prosperous New Year!

Access Visual Studio Online and Team Foundation Server projects in Outlook using TeamCompanion.

Support for Work Item Tags in TeamCompanion

You have been waiting long enough: just update your Team Explorer to Update 3 of the 2013 version and you will immediately get the support for Work Item Tags in TeamCompanion!

Work Item Tags are one of the never features in TFS which provides you the option to additionally categorize and filter your work items. Work items are easily tagged using the work item form in Team Web Access or in Visual Studio. Tags can then be used for filtering in project backlogs and work item query views.

After you update your Team Explorer to Update 3 of the 2013 version, you will immediately get the support for Work Item Tags in TeamCompanion. Tags are visible in the work item query result list and managed on the work item form.

TeamCompanion supports Work Item Tags

Filtering on tags in TeamCompanion works differently than in Team Web Access.

The TeamCompanion’s full text search applies to work item tags as well, and is precise enough most of the time. If you explicitly want to filter on a tag, you just need to be a bit more specific and use the syntax of the advanced search using work item fields in format: [Tags]=value.

TeamCompanion Includes Work Item Tags in Full Text Search Results

 

Tags are also available in the product and iteration backlogs.

TeamCompanion Shows Work Item Tags In Product and Iteration Backlogs

 

We wish you happy tagging in TeamCompanion!

Using Web Access pages as Team Project Homepages in Outlook

TeamCompanion can use any web page as the Team Project homepage embedded in Outlook. This feature allows you to display any of the pages from your project’s Team Web Access directly in Outlook.

The following set of pictures displays how several interesting Web Access pages can be used as project homepages in TeamCompanion for a Scrum based project, and which Project Home Page Configuration options you need to use:

  • the Team Web Access Home page (Choose “Use Web Access”);

Web Access Home Page as TeamCompanion's Project Homepage

Web Access Sprint Taskboard as TeamCompanion's Project Homepage

Web Access Work Item Query Chart as TeamCompanion's Project Homepage

 

The following error is a known issue when using any Web Access web page as TeamCompanion’s project homepage :

Visual Studio Online does not support your browser. Please upgrade to a supported browser to ensure a fantastic experience! Learn more.

Error Displaying Web Access Pages as TeamCompanion's Project Homepage

To work around this issue you need to edit your registry in the following way:

  • Close Outlook
  • Open regedit and open the key HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION
    (If such registry path does not exist on your computer, add all necessary keys to create it.)
  • Add a new DWORD value named “outlook.exe” with following value:
    • If you have Internet Explorer 11 installed: 11000 (0x2AF8)
    • If you have Internet Explorer 10 installed: 10000 (0x02710)
  • ¨Start Outlook

Registry Setting For Correct Display Of Web Access Pages In Team Companion

These setting will make Internet Explorer emulated inside Outlook work correctly. For further details please see http://msdn.microsoft.com/en-us/library/ie/ee330730(v=vs.85).aspx#browser_emulation.

Tip: The easiest way to enter this registry entry is to copy the following text in a text file, save it with a .reg extension, and double click it to add the settings to the registry. Windows will warn you that it is potentially dangerous action and ask whether you want to continue. Please answer yes and the error message will be gone.

        Windows Registry Editor Version 5.00 
     [HKEY_CURRENT_USER\Software\Microsoft\Internet 
     Explorer\Main\FeatureControl\FEATURE_BROWSER_EMULATION] 
     "outlook.exe"=dword:00011000

If you have any further problems regarding this feature, please don’t hesitate to contact us!

TeamCompanion 5.2 Update 1 Released

TeamCompanion v5.2 introduced the support for role-based work item views for Outlook 2010/2013 and Team Explorer 2012/2013. This v5.2 Update 1 is primarily targeted to enhance this support by introducing more powerful features for managing multiple role-based work item views.

Enhanced Support for Multiple Role-Based Work Item Views

TeamCompanion now provides the option to quickly switch between the default work item view for a user/role and additional alternative views. Some project roles need multiple different views for the same work item type depending on the context of their work. A development lead, for instance, could use an overview view by default, giving him just a subset of all information available in the work item. When discussing work items with developers, he can easily switch to the full view and access all information.

The supplementary administrative tool has been enhanced accordingly, so that now each role-view mapping, in addition to containing the name of the view used by default, can contain the list of additional views. In this case, an additional dropdown named Layouts appears on the work item form, which contains the list of all views available for the user. This list is defined by the current work item type definition and the definition of default and multiple views in the role-view mapping.

Work item form with layouts dropdown containing the list of available role-based views

 

Additionally, we have added precise view resolution rules. In other words, now you can prioritize entries in the role-view relationships table. TeamCompanion will always apply top positioned entries first.

More in depth details about managing and configuring default and multiple role-based work item views are available here.

Removed error causing the reset of TeamCompanion settings during Outlook upgrade

Local user settings, including work item mapping customizations, were reset to factory settings when certain Outlook updates and service packs were installed. This is no longer the case and settings are now preserved between different Outlook versions.

Managing Role-Based Work Item Views

TeamCompanion v5.2 introduced the support for multiple role-based work item views. Members of each user role get only the subset of work item information necessary for their work. By providing simplified views specific to different groups of users, TeamCompanion optimizes the work item user interface, simplifies it and supports a much more efficient work experience. With such an efficient user interface even the novice users can work effectively from the very beginning.

This blog discusses in more detail how to define role-based default and multiple views for different users and groups and what rules are used when a user belongs to multiple groups for which you have defined different views. It explains properties and configuration details from a technical point of view and is aimed primarily at project administrators.

TeamCompanion allows you to create different role-based views for work item forms. For example, you could have a high level overview view for your business stakeholders, which contains only a small subset of all work item fields they want to focus on, namely fields related to business value and schedule. Further views can be used by different types of subject-matter experts (SME) interested in specific aspects of the work item (e.g. specifics of the business scenario a work item relates to, quality and testing or perhaps details related to release management). The default view showing all data would be suitable for the core development team, which still needs access to all technical details.

Team administrators are provided with the supplementary tool to centrally manage role-based views for each team project (available as separate download for TFS 2012and TFS 2013). Using this tool you can define role-view mappings on three possible levels:

  • per user,
  • per TFS group, and
  • per active directory domain group.

To create an entry in the role-view relationships table, first choose a user or a group using the Add button. Then click in the corresponding cell in the column Default Layout Name to edit it, and manually enter the exact name of the view as specified in the work item type definition.

Supplementary tool for central management of role-based work item views

Basic Rules

The default view is used to display all work item types for users who:

  • do not belong to any group for which role-view mappings are defined,
  • have no directly assigned role-view mappings.

Note: The default view comes from the default work item form view which always exists in the work item type definition and is used by other TFS clients such as Team Explorer or Team Web Access.

Only one role-view mapping entry for each user and group can be added to the table.

When a user or a group has a role-view mapping defined, TeamCompanion does the following when deciding how to display each work item:

  1. If the work item type definition contains the view matching the one stated in the Default Layout Name column, then this view is used.
  2. If the work item type definition does not contain the view matching the one stated in the Default Layout Name column, then the default view is used.

After a user or group is assigned a view, they need to (re)start Outlook for these settings to apply.

Defining Views over More Work Item Types

A simplified view targeted to a particular group of users, for example business stakeholders, may be used in several work item types. In other words, a stakeholder using a high level overview for a User Story, will need a high level overview for a Task as well. As a consequence of the basic rules stated above, you can achieve this is in the following way:

  1. Edit the definition of the User Story work item type and define a custom user story view for your stakeholders. Let’s name it Stakeholder View.
  2. Edit the definition of the Task work item type and define a custom task view for your stakeholders. Name it using the same view name as in the User Story, Stakeholder View.
  3. Add an entry to the role-view relationships table, specifying the group your stakeholders belong to (or a particular stakeholder) and reference the Stakeholder View in the Default Layout Name column.

Note: The number of views defined within each work item type definition is not limited.

Using Multiple Views

Until now we have explained how the view stated in the Default Layout Name column is used as the view of choice for the corresponding user or group referenced by the role-view mapping.

Some project roles can use multiple different views for the same work item type. A development lead, for instance, could use an overview view by default, giving him just a subset of all information available in the work item. When discussing work items with developers, he can easily switch to the full view and access all information.

TeamCompanion provides the option to use such multiple views as well. Alternative views are defined in the column Other Layouts as a semi-comma separated list of work item type view names. The default work item type view is referenced using the syntax {Default}.

The following example references the default view and another 2 views:
{Default};All in view (Devs);Just the content view (SME)

To add multiple views to an existing entry in the role-view relationships table, click in the corresponding cell in the column Other Layouts to edit it, and manually enter the semi column separated list of view names.

Supplementary tool for central management of role-based work item views

When a role-view mapping contains the definition for multiple views, then an additional dropdown control named Layouts appears in the toolbar of the work item form. It contains the list of all views available for that user. This list is defined by the current work item type definition and the definition of default and multiple views in the role-view mapping.

Work item form with layouts dropdown containing the list of available role-based views

 

More precisely, the list in the Layouts dropdown is an intersection of the set of views from the work item type definition and the set of views which is the result of the union of the default and all multiple views defined in the role-view mapping.

The following table contains a few examples to clarify there rules:

Process Template:
Views in the
work item type definition

Admin Tool:
Default Layout Name
column

Admin Tool:
Other Layouts

column

TeamCompanion:
Layouts

dropdown list

{Default}
All in view (Devs)
High level overview (CxO)
Just the content view (SME)

All in view (Devs)

{Default}
High level overview (CxO)
Just the content view (SME)

{Default}
All in view (Devs)
High level overview (CxO)
Just the content view (SME)

High level overview (CxO)

All in view (Devs);

All in view (Devs)
High level overview (CxO)

{Default}

High level overview (CxO)

{Default}
High level overview (CxO)

All in view (Devs)

High level overview (CxO)
View_A

All in view (Devs)
High level overview (CxO)

All in view (Devs)

View_A
View_B

-

As you can see from the examples, for work item types containing at least one of the multiple views, the Layout dropdown will be visible. The dropdown will not appear when just a single view is valid for the work item type after resolving all rules.

Note: In case the view specified in the Default Layout Name column does not exist for a work item type, then the default view for that work item type will be used, no matter it the type contains any of the multiple views.

View Resolution Rules

More than one entry from the role-view relationships table can apply to a single user. For example, a user can have directly assigned role-view mappings and he can be a member of the group which has its own role-view mapping. Or a user can be a member of two groups both having their own role-view mappings assigned.

In order to define which views are valid in such cases, TeamCompanion offers the option to prioritize entries in the role-view relationships table. Using the up and down arrows on the left of the table, the order of table entries can be adjusted.

TeamCompanion uses following rules for view resolution:

  • Top positioned entries are resolved first.
  • If more entries apply to a single user, then only the highest prioritized mapping will be used. Other mapping will be ignored.
  • When the order of entries in the role-view relationships table is changed, then users will get new mappings after they restart Outlook.
    Note: Depending on the order of performed actions, the first displayed view will most probably be the old one (from the cache). Once validated against server, new view will be used instead.
In the following example, Julia has a particular view mapped to her user credentials. In the same time she is a member of the TFS Development Team. In this case, TeamCompanion will use the Julia’s View.
    User/Group Default Layout Name
    Julia Ilyiana Julia’s View
    TFS Development Team Team View

In case the order of the views is changed, as in the following table, TeamCompanion will use the Team View for Julia.

    User/Group Default Layout Name
    TFS Development Team Team View
    Julia Ilyiana Julia’s View

In the following example, Julia is member of both TFS groups, Development Team and Web Team. As the mapping for the Development Team is listed first in the table, TeamCompanion will use the Team View for Julia.

    User/Group Default Layout Name

    Development Team

    Team View

    Web Team Web View

If you have any further questions regarding the management of role-based work item views, please don’t hesitate to contact us!