These enhancements to our JIRA integration support provide more flexibility and allow users to re-use the workflows across multiple teams that have different JIRA setup and requirements.

Variable support for all types of custom fields

Users can now provide variables for all types of custom fields including Select (drop-down) and fields that take multiple values as well.

Support for time tracking fields

Users can now provide estimates when they create or update JIRA issues using the JIRA step. Variables are also supported for the estimates.

Support for setting Resolution

Users can set Resolution when they are updating a JIRA issue. Again, variables are also supported for this field.

Refer to our docs for more details.

Users can now configure Docker, Nexus or Helm artifact sources via GraphQL APIs! Really helpful when trying to automate the creation of artifact repositories for Harness to use.

CreateConnector($connector: CreateConnectorInput!) {
  createConnector(input: $connector) {
    clientMutationId
    connector {
      ...on DockerConnector{
      name
      id
      }
    }
  }
}

In our API Explorer, it can be found in the mutation section under CreateConnector

Check out our docs!

Users can now define their own Deployment Types that are not provided by Harness out of the box. Custom Deployment Type allows users to configure their entire deployment to match their specific environment. These Custom Deployment Type Configurations can be managed in the Template Library and shared with other teams!

Please see our docs!

Users can now manage their ECS Delegates in a Group. All live delegates will appear in the group while disconnected delegates will be hidden. Our users tend to place their ECS delegates behind autoscaling groups so delegates will spin up and down. These configurations can be contained and managed now! As delegates register with Harness they will be grouped based on the group name provided during delegate download.

Delegates that are not associated with a group are classified as "Autonomous"

Harness users can now deploy Custom Resources as Managed Workloads for Kubernetes and Openshift. Users can now configure a Rolling Deployment to deploy their Custom Resources and have Rollback Capabilities. Harness also checks the steady-state of the deployed Custom Resource to make sure the Custom Resource container is healthy. The deployed Custom Resources will be visible in the Service Instance Dashboard for users to track.

Check out our docs

Users can now access their ECS Task Definition and Service Definition in Git and manage them outside of Harness. These ECS Task Definitions and Service Definitions can contain Harness variables and Harness will populate them at runtime and deploy the task.

See our docs!

CE users who are connected to a GCP account may now view the discounts (due to Committed, Sustained usage) as part of the overall cloud bill.

Harness CE now provides users an option to select specific columns from any table. The selected columns may also be exported via the CSV functionality.

Harness users can now create and setup deployment triggers using GraphQL API. This improvement makes it much easier to onboard new applications in an automated way, without the need of setting the triggers using the graphical interface.

When generating a Terraform Plan from an Infrastructure step, can be passed to a subsequent Infrastructure Provisioning - Terraform step for deployment. With this, users can view the plan and confirm that its an approved plan that's going to be used in the Apply step for actual infrastructure provisioning.

Read Our Documentation