In Craft.io's latest release, we've launched several practical tools that will help ramp up your team's efficiency, as well as introduced an exciting improvement to our Jira integration with multi Jira Project integrations.
In Craft.io’s latest release, we’ve launched several practical tools that will help ramp up your team’s efficiency, as well as introduced an exciting improvement to our Jira integration with multi Jira Project integrations.
Let’s take a quick look at these updates:
Multi Jira Projects & simplified integration process
Over the past six months, we have been working hard on improving our data model so that it better reflects our customers’ needs and scales with them as their product teams grow. A major part of that change was to shift most of our users to a single Workspace environment, the benefits of which are clear. Using one Craft.io Workspace means everyone has a single product source of truth and a collaborative space to work together, manage dependencies, and create product transparency. But, we had one thorny point! You could only connect a single Workspace to a single Jira project, which was not realistic for many of our customers.
With the launch of our latest release, this is no longer the case– you can now integrate a single Workspace with any number of Jira projects.
An example of integrating a single Craft.io’s Workspace with multiple Jira Projects
As well as the new multi Jira Project integrations, we’ve also made meaningful improvements to the set-up process and have simplified the setup process so that doing so is easier and more intuitive. Check out the step-by-step Jira integration guide here.
Save time by syncing in bulk
In this release, we’ve also added the ability to bulk sync your items. From now on, you can multi-select items via the table or kanban views, and sync them all to their corresponding Jira Project in a single click.
Create Custom Groupings to display the data your way
One of the main benefits of using Craft.io is the ability to build views that product, development, and other stakeholders like leadership, CS, sales, and support teams can rally around. To date, you’ve been able to do us by using our powerful Table, Kanban, and Timeline boards to show your data in a way that is relevant to your audience. Today, we are supercharging these boards with Custom Grouping, the new power tool converting dev work into product clarity!
Custom grouping is simple but powerful – it allows you to add a selection type custom field to any data item you have in the system, and then group your view by that group. For example, let’s say you are the PM responsible for the product ZalesLoft, a highly successful sales engagement platform. Your company works across different regions (NA, LATAM, APAC, EMEA), and you’re about to head into a regional leadership meeting where you need to outline each regional plan. Sounds familiar? Well, if in the past you had to dig through the mess of your Jira data, export items to Google sheets, and organize the data in a neat presentation, you can now achieve the same result in a couple of clicks. Thanks to custom groupings, you can easily and quickly create a compelling board to show your regional leadership all without breaking a sweat.
Filter your views by specific team members
Craft.io enables users to add to Sections, Features, and Sub-Features a variety of custom field types, such as text, number, date, and selection from a list. These custom fields are very powerful as they enable users to define, differentiate, and filter the various items in the system. Today we have added a new type of custom field: Team members.
In addition to the preset team member fields that already exist in the system, like “Created by” and “Assigned to”, users can now add team member custom fields, populated from the existing users and teams listed in a Craft.io Workspace. This is useful when the person or people responsible for a task does not correlate with who created the item or with the person it’s currently assigned to within the workflow process. For example, you could create a custom field that includes a PM, technical project manager and a scrum master, and then filter your view by that group or by the individual team members of that group.