This information is specific to the 2022.1.2 Flow Enterprise Server release.
- Flow Enterprise Server now includes Flow’s Delivery Module. This set of reports, including Ticket log and the Retrospective report, help you deliver value to your customers with additional insights into your ticketing system. Use these insights to manage the workflow and efficiency of your teams. The Delivery Module requires some configuration and set-up to work best for you.
- Now you can access the Proficiency report to gain insight into your team’s proficiency in a specific coding language. Use this report to view code commit efficiency trends for the most prevalent software languages used in your code repository.
- Flow Enterprise Server requires a single, raw block device for Ceph storage usage on every node in the cluster. This is required for both new installations and upgrades.
- To ensure stability of Flow, implement a three-node cluster to provide protection from node failure, disk failure, and volume corruption.
- If you’re upgrading an installation from 2022.1.1 to 2022.1.2, upgrade through the KOTS admin console. Read more about upgrading to Flow Enterprise Server 2022.1.2 for more details.
- If you’re upgrading to 2022.1.2 from a Flow version earlier than 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 for Flow Enterprise Server 2022.1.2 for more details.
Features and major changes
- When setting up Delivery module:
- By default, users with the Team lead or Admin role have access to the Delivery module. To enable the reports for other users, make sure they have the Ticket log and Delivery Retrospective permissions. To allow a user to edit ticket configurations, make sure they have the Manage Delivery Configuration permission. Learn more about assigning permissions to roles.
- If you’re not seeing data how you expect, check the status of your ticket projects. Go to Settings, then Ticket Projects to view your ticket configurations. Next to each project you’ll see a status. If the status is red or yellow, it’s a sign your data is not being ingested correctly. Click on the status link to view options to resolve any ingestion issues. Learn more about configuring ticket projects.
- If data from some users isn’t showing up in the reports, double check the permissions on your teams. Make sure the team member permissions for each user is set to Contributor. If a team member has the Viewer permission, their data will not appear in any of the Delivery Module reports.
- If you’re not seeing your finished tickets, double check that none of your ticketing system done states are set to canceled in the ticket project configuration. Tickets in a canceled state are not shown in the Delivery Module reports.
- When setting up the Proficiency report:
- By default, users with the Team Lead or Admin role have access to the Proficiency report. To enable this report for other users, make sure they have the Proficiency permission. Learn more about assigning permissions to roles.
Resolved issues and miscellaneous updates
- Organizations missing when trying to import GitHub teams
- Users with View own teams view rights unable to search for team names
- Errors when setting the default domain on Settings Home
- Unable to create new repo tags
If you need help, please contact Pluralsight Support.