May 28, 2022 - JiHu GitLab  
15.0

JiHu GitLab 15.0 released with WYSIWYG for Wiki, container scanning in all tiers

JiHu GitLab 15.0 with container scanning now available on all tiers, internal notes for issues epics, linking external organizations and contacts to issues, JiHu GitLab SaaS runners on macOS and much more!

Today, we are excited to announce the release of JiHu GitLab 15.0 with container scanning in all tiers, internal notes, better links to external organizations and contacts, and much more!

These are just a few highlights from the 40+ improvements in this release. Read on to check out all of the great updates below.

Key improvements released in JiHu GitLab 15.0

JiHu GitLab 15.0 includes a few exciting improvements to speed up your workflow in the WYSIWYG Markdown editor for your wikis.

First, you’ll find no more un-styled, monochrome code blocks: choose from over 100 languages in the dropdown list above the code block so your CSS, YAML, and Python code are distinct from each other with accurate syntax highlighting. The code blocks will even inherit your preferred syntax highlighting theme. You can also quickly copy the code block to your clipboard for use in your code editor of choice.

You’ll also find working with links and media in the WYSIWYG editor easier than ever. Previously, you had to select from the editing toolbar to change a selected link or image on your wiki page, with some edits requiring you to delete the link or image and re-create it. Editing links and images is now easier, with a new popover menu that appears when you select a link or attached image. From the menu you can quickly edit a link’s destination URL or description, copy the link or image to your clipboard, or even remove the link or image from the page.

Edit code blocks, links, and media inline in the WYSIWYG editor

Advanced Search is compatible with OpenSearch

OpenSearch is an open source Elasticsearch fork. Prior to JiHu GitLab 15.0, Advanced Search was not compatible with OpenSearch. If you used AWS-managed services, you had to use older versions of Elasticsearch. You can now take full advantage of OpenSearch for Advanced Search.

Advanced Search is compatible with OpenSearch

Plan and schedule issues with automated iteration cadences

In JiHu GitLab 14.10 and earlier, groups supported only one set of iterations. It made it difficult for different teams that worked in a single group to have autonomy with scheduling and tracking their issues from iteration to iteration. To improve this, we’re adding the ability for a group to manage multiple sets of concurrent iterations with iteration cadences. This allows each team to have control over the start day and duration of each iteration in their iteration cadence.

The day-to-day management of iterations is now much more efficient too. When you create a new iteration cadence, select the first day of your first iteration, how many weeks each iteration should be, and how many upcoming iterations JiHu GitLab should maintain for you. You can also optionally enable unfinished issues to automatically roll over from one completed iteration to the next. After a cadence is created, JiHu GitLab automatically creates the specified number of upcoming iterations.

You can now also scope an issue board or issue list to an iteration.

All existing iterations in a group will be converted to an iteration cadence with no changes to underlying iteration data. Additionally, to better support future enhancements to iterations, such as iteration velocity and volatility and capacity planning, we’ve deprecated the ability to manually create and delete individual iterations and will remove this functionality in 16.0. Learn how to migrate to automated iteration cadences.

Plan and schedule issues with automated iteration cadences

Internal notes

In many cases, organizations want to keep issues and epics public, but apply stricter governance to conversations within them. For example, when using JiHu GitLab issues as part of Service Desk workflows, organizations may want to make core details about an issue public, but not to expose customer-specific confidential data broadly.

With internal notes, you can redact discussions with internal or customer data that should only be visible to certain users, while keeping the core details about an issue public. Internal notes in issues or epics can only be seen by the issue author, assignee, and group or project members with at least the Reporter role.

Thanks @leetickett for collaborating with our team on this feature!

Internal notes

JiHu GitLab 15.0 introduces the first MVC toward managing and billing external customers from JiHu GitLab. With the customer relations management (CRM) feature, you can:

  • Create organizations and contacts.
  • Set a default bill rate for an organization.
  • Add contacts to organizations.
  • Link contacts to issues with the /add_contacts quick action.
  • View issues associated with a given contact or all contacts belonging to an organization.

The customer relations feature is not enabled by default, and can only be managed from a top-level group. If you want to help shape the future direction for customer relations management within JiHu GitLab, please contribute to this issue.

Thanks @leeticket for the dozens of contributions and countless hours spent leading this effort!


Container Scanning available in all tiers

Container Scanning helps developers to easily find known security vulnerabilities in dependencies that are installed in their container images. With JiHu GitLab 15.0, we are making the basic Container Scanning features available in every JiHu GitLab tier.


Use nested CI/CD variables with environments in pipeline configuration

Using CI/CD variables with the environment keyword in your CI/CD configuration is great, because it lets you create environments dynamically. While this is already a powerful feature, there were still some limitations, because you could not use nested variables to define environments.

Starting in JiHu GitLab 15.0, you can nest variables inside other variables, and have them all expand the way you expect. This makes dynamic environments even more powerful due to the increased flexibility!

Use nested CI/CD variables with environments in pipeline configuration

Believe it

Get unlimited access to all JiHu GitLab Premium features for 60 days.