In this release, the following features and enhancements are made available to the customers. This release is available for both Kendis Cloud and Kendis Self Hosted Customers.

It is now possible to set the color for the feature cards, previously feature type was always shown as a card with a white background. It is also possible to set the background and text color for the story cards.

Feature and story card colors are board specific and it's possible to edit the colors for the existing boards by going to the "Edit Board Settings" menu option and going to the "Details" tab.

There are more colors for additional card types. The same color scheme for card color and text color is available for features and story cards.

In Jira, it's possible to use the same sprint on multiple boards. It provides some benefits as an organization can start and close a single sprint that is used by multiple teams.

With this release update, now it's possible to use the "Shared Sprint" at Kendis and use an additional field to distinguish between different team contents. Kendis supports "Standard Jira fields" for this purpose. For example, you can use a custom field like "My Jira Teams" or more commonly organizations use the "Component" field to separate boards for teams.

Kendis uses Jira REST API for integration between Kendis and Jira. Previously for Jira Server, only "Basic Authentication" was supported, which means users have to enter their Jira credentials to connect to Jira.

If you are using the Jira Server version, you can use the "oAuth" authentication method, which means your users don't need to provide the Jira credentials at ALM or at their profile. Support for oAuth is only available to "Enterprise Pro" and "Cloud Premium" customers. In case you want to get more details about Jira oAuth support, contact us at support.
​

Previously, if a feature or story is removed from the sprints on the board the dependencies associated with these items will disappear.

With this release, the dependency will be restorable if an item is removed accidentally or intentionally from the sprints on the board

Similar to dependencies, if a feature is removed from the board, then the linking to the objectives will be removed as the item is not on the board.

With this release, you will be able to identify if a feature or story is removed from the board. Kendis will show the ID of the item and you can click on it to view it in Jira.

Once you bring the feature/story back to the board, the linking will be restored automatically

Example: "DP-71" is removed from the board and it was linked to the objective

Once the feature DP-71 is added back to the board, objective linking will be restored automatically

In AzureDevOps and TFS there is a concept of "Default Backlog Iteration" and when an item is removed from the team sprint, it should move to this default backlog iteration. Previously it was not supported at Kendis and removing a story from the sprint will be moved to the root path.

With this release, each team's default iteration will be used when a story is removed from the sprint at Kendis.

In case your default backlog iterations are not set for your teams, you can check this setting under the "Edit Board Settings" and Teams tab. If you click on the "Update All" under Backlog iterations, it will automatically update values for all the teams that are mapped at the Kendis board

AzureDevOps and TFS provide flexible ways to use Areapath. Previously, at Kendis you would need to select the Areapath at team mapping and if the story moves from one team to another then the Area path would be updated accordingly. Customers wanted more flexibility to control this behavior and with this release, now you have the ability to disable the Areapath synchronization. If this option is selected at the team mappings you can't select the Areapaths and additionally, you can't map the same sprint to multiple teams.

The sprint filter in the comparison and data reports section was missing previously due to some limitations. It's available with this release. Sprint filter enables the customers to filter the features and stories for a particular sprint in the reports.

Scaled Agile Framework has renamed stretch objectives to uncommitted objectives in the SAFe® 5.0 update. Kendis team kept it on the previous terminology as the stretch was easier to understand, however, based on the customer feedback, we have now changed the label to "Uncommitted Objectives".

At team mapping, customers should select under type, item type for their User Story, but often customers selected item type for their features, e.g., Epics.

This default selection is the item type selected when at the boards you click on the "Add Story" button. So it's quite important to select the correct item type, so when your teams create new stories, they select the correct item type by default.

This is just a default selection, while creating a new story, you can also select different item types that are supported in your project.

Default selection at the "Add Story" option under feature at team board

To provide better support for different kinds of active directory setups, Kendis has released a new version of it's LDAP support. In this version, when configuring your LDAP configuration, you can mark additional user DN as an option and don't have to provide it. Also, the system will detect the other settings automatically based on authenticated users.

Self-hosted Kendis Build is updated with the following version
​Version:202007-3.0.2
​Build Version: 6341bb74c1b758555f02c9686dadafb02373bbf9