Flow Enterprise server release 2022.1.1

Tags: Flow on-prem

This information is specific to the Flow Enterprise Server 2022.1.1 release.


Important notes

  • Flow Enterprise Server now requires a single, raw block device for Ceph storage usage on every node in the cluster. This is a requirement for both new installations and upgrades.

  • In order to ensure stability of Flow, Pluralsight recommends that customers implement a three-node cluster to provide protection from node failure, disk failure, and volume corruption.

  • If you’re upgrading from a previous Flow version to 2022.1.1, you must reinstall Flow from the command line. You cannot upgrade through the KOTS admin console. You must export your Flow configuration, uninstall Flow for all nodes, then reinstall Flow. Read the article about upgrading to Flow Enterprise Server 2022.1.1 for more details.

back to top


Features and major changes

Reports

  • In Review Workflow, Work log, and Player card you can now filter for deleted PRs.

  • Now you can see Time to merge in Submitter fundamentals and Time to first comment in Reviewer fundamentals. Using these metrics leads to better outcomes for leaders, teams and individuals. Having them in the fundamentals reports means you can find them faster, along with the other metrics you use.

  • Now only merged pull requests will be counted toward your metrics in Reviewer fundamentals, Submitter fundamentals, PR resolution, Review Collaboration, and the Reviewer and Submitter fundamentals sections of Player Card. This will lead to a more accurate view of collaboration work and a more consistent experience across reports.

Note: If you were previously looking at pull requests with statuses other than Merged in these reports, your historical metrics may look different.

  • Time to close and Time to resolve have been renamed to Time to merge. These metrics calculate the same thing, so the names have changed to be more consistent across the platform.

  • Flow now has a page called Settings home. On this page, new organizations can find the steps they need to get set up and start importing their data. Existing organizations can find helpful links to commonly used settings.

Data ingestion

  • Now Flow uses integration-level processing to process your most relevant data first so you get a complete picture of your work. This processing prioritizes the most relevant information and means you will see a fuller picture of your data instead of randomly selected data while the data from your integrations is still processing.

Infrastructure

  • Now the Frontend, Integrations, and Worklog BC database fields in the KOTS admin console have been consolidated into a single set of fields to make configuring your database easier.

back to top


Patch release updates

  • 2022.1.1-1: Resolved issue with SSO role binding.

back to top


Resolved issues and miscellaneous updates

  • Added additional remediations for log4j vulnerabilities.

  • Fixed a file permissions issue in the storage directory when upgrading from an older version.

  • Worker pods starting on the primary node even when the worker= label is only on the worker node.

  • Daily digest emails not being sent.

  • Unable to see weekend data in Project Timeline.

  • Page turns white when trying to create a new Slack rule.

  • Unable to select calendar date and time for Messages settings.

  • Unable to update your avatar.

  • Unable to see Admin Alert emails in Outlook.

  • Issue with calculating New work, Legacy refactor, Help others, and Churn in Snapshot. In some cases, commits were duplicated for pair and group commits. The impact of the change should be small, but you might see a decrease in the total number of commits displayed in the Snapshot report.

back to top


If you need help, please email support@pluralsight.com for 24/7 assistance.