Defect fixes

Fixed issues with displaying of newly created environments on the Pipeline page. Previously, when you added an environment, without refreshing the page, the added environment was displayed.

Fixed issues with displaying of the deployed solution version in the deployment pipeline. Previously, when you deployed a solution version to an environment in the pipeline and deleted the jobs associated with that environment, the deployed solution version was still displayed on the deployment pipeline.

• Insights results on the Insights page.
• Pipeline page.
• Create task dialog on the Deployment plan page.
• Home page.

Fixed issues with Approver gates in the Deploy stage for API driven applications.

Fixed issues with deployment of old versions to different environments in the pipeline for API-driven apps. Previously, you were not able to deploy an older version of an API-driven App to a different environment in the pipeline after deploying a newer version.

Fixed issues with adding an Ansible task to a deployment plan. Previously, when you added an ansible task to a deployment plan, the page got crashed.

Fixed issues with incorrect status displayed for release activities on the Releases page. Previously, the release activities with Failed status is displayed as In Progress on Releases page.

Fixed issues with creating version records for the deleted applications. Previously, version records are getting created for the application which are deleted from the pipeline.

Fixed issues in displaying the permissions for the Lead developer role. Previously, the Archive permission checkbox for Deployment template was not displayed for the Lead developer role.

Fixed issues in displaying error message while creating a solution version with the same name as the existing solution version.

Fixed issues with displaying deleted applications in draft solution versions. Previously, the applications deleted from the pipeline were displayed in the draft solution version.

Fixed issues with display of error messages while creating a UrbanCode Deploy Status task with missing fields. Previously, when you create an UrbanCode Deploy Status task with missing fields and try to save the task, different error messages were displayed for missing different fields.

Fixed issues with events appearing as a release on Join Release modal. Previously, whenever a event is added in the calendar on Releases page, the event was appearing as a release and available for selection on the Join Release modal.

Fixed issues with saving the changed roles for members of a team. Previously, when you try to edit the roles for the members in a team, you could not save the changes by pressing the enter on the keyboard.

Fixed issues with the alignment of table column headers while scrolling on the Deployment Plan details page.

Fixed issues with the highlighting of missing fields while creating a release. Previously, when you try to create a release with missing fields the error message was displayed for missing fields, but the fields are not highlighted.

Fixed issues with closing of Edit task dialog. Previously, when you click outside the Edit task dialog, the dialog was getting closed.

1. Integrations
2. Create user
3. Add roles
4. Create User Access Key
5. Settings

On the Pipeline page with HCL® Launch applications added to the pipeline, when you change the name in HCL® Launch, the name change is accurately reflected on the Pipeline and the Dashboards pages in HCL Accelerate.

• Click Authentication > LDAP.
• Click the Import users button.
• In the Username or Pattern field of the Import Users window, when you enter a username or pattern and then click the Save button, resolved a query size limit exceeded error during the attempted import process.

• Insights page not loading.
• VSM not loading.
• Plugin containers not being removed after execution.

• Click on the Reports tab.
• Click on the required report.
• Click on the Results link of a previously run report or click the Run report button to generate a new report with a Results link.
• When you share the report link, the server port is used versus using the assumed port number 443.

• Click on the Reports tab.
• Click on the Deployment audit report.
• In the Deployment audit window, click in the Timezone drop-down field and select the Coordinated universal time (UTC) required for the report.
• In the Deployment audit window, fill in the remaining required fields.
• Click the Confirm button to run the report.
• Click the Results link to display the Deployment audit report in the selected time zone.

• Click the All dashboards or My favorites tab.
• Click the required dashboard.
• Click the Add charts icon.
• For the required chart, click the +Add button.
• For the added chart, when you click the filters icon, all of the available filters for the chart are properly displayed and functioning.

• Click the Reports tab.
• Click the Release readiness report.
• Click the Click the Run report button.
• In the Release Name (optional) drop-down field, when you manually type a partial release name, the field populates with the related query names.

• Click a release activity.
• Click a deployment plan.
• Click the Create task button.
• Click the Type drop-down and select Wait for approval.
• In the Create task window, fill in the required fields.
• Click the Save button.
• For the Wait for approval task, click the Start task icon.
• Receive the email and click the Approve button.
• If the email address of the approver matches the user logged into HCL Accelerate, the message You have approved this request. is displayed.
• If the email address of the approver does not match the user logged into HCL Accelerate, the message Your action could not be completed. Please contact support if the problem persists. is displayed.

• Click the overflow menu for a required release activity and then click Archive.
• The release activity is archived after it is clicked once.

• Release activity
• Deployment plan
• Edit icon and the Automatically approve the deployment checkbox does not appear in the Edit plan window.

• With exception to the Input environment, click the required release link under an environment in the pipeline.
• The deployment plan detail page opens.
• Resolved issues where Jenkins tasks were restarting due to parallelization of prior tasks.

• Click Add application and add a Jenkins integration with a long Application name.
• On the Jenkins app for the Input environment, click the overflow menu and select Create version.
• In the Create version window, resolved UI positioning errors of the application and job selection screens on the pipeline.

• Select a team containing more than 25 members.
• In the Items per page drop-down, select 100.
• Click the overflow menu and select Assign roles.
• In the Edit member window select a Role and click Save. After saving, the page size correctly reverts to 100 items per page as previously selected.

• In the Release activities table, click on a release.
• For the required deployment plan, click the overflow menu and select Edit this plan.
• In the Edit deployment plan window, when you click the Team drop-down, the field is populated correctly with the associated teams.

• In the Release activities table, click on a release.
• Click the Create deployment plan button and create and save a deployment.
• Click the deployment plan created in the previous step.
• Click the Create task button and create several Jenkins tasks.
• Schedule deployment in five minutes.
• For the created deployment plan containing the Jenkins tasks, click the Complete task, Fail task, and Skip task icons to confirm the aforementioned states. When the START TIME occurs, it is ignored because the deployment plan is in progress.

• When you have the appropriate permissions, you can click the overflow menu and select either Edit or Delete value streams.
• When you click Enable drag, you can drag stages.

• When you run a Jenkins task, you instantaneously know if it does or does not run without dependency on heartbeat performance.
• When a user navigates to a deployment plan with dynamic roles enabled and insufficient permissions prevent viewing the deployment plan, a notification is displayed that indicates you do not have permissions to view the plan.
• When you click Archived, in the Name field, an actual name is displayed for each archived release.
• For Wait for approval tasks, when you select an LDAP group, the NAME field displays an actual name.
• When viewing a release with new permissions implemented and the user has permissions to a release, the You do not have sufficient permissions to view this page Contact your administrator for necessary permissions. dialog is not displayed.
• Regardless of team assignments, users are able to view deployment templates. In future versions, viewing deployment templates are secured with the appropriate permissions.
• While editing a deployment plan, release, or template, when you click the Team drop-down, you can select any team in the list.

• When you click Authorization > Roles, team roles are displayed correctly.
• The Email server and LDAP and SSO Authentication pages are working properly and updating associated permissions. If you migrated to HCL Accelerateversion 3.0.0 and are experiencing permission assignment issues, contact support.

• Using Git branching strategy for writing, merging, and delivering code.
• When squashing commits are not performed prior to merging.

• Value streams
  • If a work item status contains a leading number and a DQL query references that number, stage change event calculations yield correct results.
  • If deployment data from plugins is not having data properly converted when creating history, value streams properly load when using either HCL® Launch or Microsoft Azure.
  • On the Value Streams page displayed in the Chinese language and when you click on any of the filter drop-downs, the page filters properly according to your selection.

• Pipelines
  • For either HCL® Launch or Microsoft Azure apps with passed automated gates, passed versions remain green with introduction of any number of new versions. On any environment except Input, when you click Add gate, modal UI text is updated for clarity.
  • Gates failure no longer alternates between the two same jobs in any environment.
  • If API-driven pipelines and auto promotion are set up simultaneously, both operate properly without issues.
  • On the Pipelines page, resolved an issue with duplicate pipeline deployments occurring when both autopromotion and gates were configured on the same environment.

• Fixed security vulnerabilities.
• When you click and then select Getting started, the drop-down closes properly.

• When you click the overflow icon and select Lock, the lock icon is displayed before the release name.
• When you:
  • Select a release.
  • Select a deployment plan with Jenkins.
  • Click the Create task button.
  • Create and save a Run a Shell Script task.
  • The shell task is added to the deployment plan successfully.

• Updated the UI for an enhanced user experience.
• Long release names are truncated with ellipsis.

• When you hover over a dot existing in multiple stages, a unique ID attribute will display based on the stage where the action is performed.
• Removed faulty display component appearing behind header.
• On the dot details panel, the title is fully displayed.
• When the window size changes, dots display inside the respective stages.

• Dots display correctly without overlap.
• When you collapse an expanded phase, click on a field containing multiple dots, click an arrow for one of the dots, only one dot detail panel is displayed.

• Value streams
  • On the Swimlane page, when you click either the phases, stages, or any items in the dynamic row selector and hover over the time in stage, null is not displayed.
  • When you click Value Streams > Add new value stream, enter and save information in the required fields of the Create a Value Stream window, delete the aforementioned value stream, and either: refresh the page, click All Value Streams, click My Favorites, a blank page is not displayed.
  • On the Swimlane page, when you click on a dot, the panel points to the column where the dot is located.

• For the example DQL filters in the following table:

  Filter	DQL query
  1	issue.status='In Progress' AND pr.source!=GitHub
  2	pr.status=open AND pr.labels!='Any Label'
  3	pr.status=open AND pr.reviews.count=0
  4	pr.status=open AND pr.reviews.count>0

  When Filters 3 and 4 are combined with Filter 1 with the OR operator, Filter 1 dots are displayed. When Filters 1 and 2 are combined, the data is filtered properly.

• Value streams
  • When you click Value Streams > All Value Streams and then click the tabular list icon for value streams in a narrow window, the table heading metric fields truncate and you can hover over the fields to display a pop-up detailing the metric names with definitions.
  • On the Value Streams page, when you click a value stream and click either Expand or Collapse, the up and down arrows are pointing in the correct direction.
  • On the Value Streams page, when you click a value stream and click the Release or Sprint filters and select a release or sprint that is not in one of the five most recent, a blank page is not displayed.
  • On the Value Streams page, when you click a value stream and click the Commit or Pull request filters and select a pull request or commit, the pull request and commit filters remain selected after the page reloads.

1. Determine the memory requirement.
2. Under spec > template > spec > containers in your yaml file, locate the line image: urbancode/velocity-se-release-events-api:x.x.x.xx.
3. Add the command override as a sibling entry to image: in the form of the following:

   
        image: urbancode/velocity-se-release-events-api:x.x.x.xx
        command:
          - node
          - --max-old-space-size=xxxx
          - /release-events-api/release-events-api.min.js
            

4. On the command line - --max-old-space-size=xxxx, enter the maximum memory requirement in the appropriate units.