Kanban View of Work Items
Kanban view is like a visual roadmap for managing tasks and Work Items.
It organizes Work Items into cards on a board, providing a clear, at-a-glance overview of the entire process.
Each card represents a task or Work Item, and users can easily track progress, move deployments between different stages, and collaborate effectively.
The Kanban view is especially beneficial for teams practicing agile methodologies, as it enhances transparency and helps streamline the workflow.
Transferring cards from one board to another is currently not possible.
New User-level Deployment Options
Users can now customize their deployment options on an individual basis (Team owners, Team leads, developers) by accessing "Default Deployment Options" in their Account Settings.
In addition to Profile, Git Branch and Git Commit users can set individual Test levels, Notifications through Slack and Microsoft Team.
These modifications will be implemented for any new deployment initiated from the user's account.
Back Promotions (Beta)
A back promotion is a process that allows for the selective deployment of work items (or a deployment) from higher environments to lower environments.
With a back promotion, you can minimize differences between orgs from a metadata perspective and decrease merge conflicts.
For example, a developer can back promote changes deployed from another lower environment into an upstream environment to keep their org in sync.
To request access to this feature, contact Essentials Tech Support.
Better handling of Custom Labels in CI Job
In the past, modifying a custom label and deploying it would result in the entire file being deployed when the CI job with "Deploy from last successful build" was activated. Now, we specifically compare the altered lines of code, ensuring that only the differences are deployed to the target.
As shown on the screenshot, only the 2 modified Custom Label are deployed instead of all the custom labels in GIT.
Cloning a Work Item into a Standard Deployment
In this release, there is a new feature to allow user to clone a work item into a new deployment.
On the work item screen, user can click on “More > Clone To Deployment” to clone the current Work Item into a new Deployment.
This provide flexibility for users to deploy the same Work Item change set to any other Org (eg. back promote the Work Item change set to any other Sandbox).
Deployment Tasks (Beta)
Deployment tasks ease pre/post deployment operations.
For example: Sending emails or Outgoing webhooks as part of a deployment.
Reduces manual work of developers.
Can accomplish multiple tasks in a single deployment
Provides documentation for deployment related activities
Note: this feature is currently only available for standard deployments. Work Items and Deployments with Pull Requests do not support Deployment Tasks.
To request access to this feature, contact Essentials Tech Support.
Happy Deploying!!