Understanding Jira Work Management

[#1]

Jira Work Management

Jira Work Management (JWM) is aimed at business teams like HR, marketing, and Sales. Atlassian’s goal here was to gather every department in Jira, along with development and operations, working in Jira Software and Jira Service Management.

JWM brings about significant UI changes and custom views that make work in Jira easier for less computer-savvy users while bringing the tools that they work with every day, be it forms, Gantt charts, or spreadsheets. Still, its new features do leave room for improvement in the area of true customizing. Let’s review what Jira Work Management brings.

Use Cases

The first thing that will catch your attention in JWM is the sheer number of project templates. The “Business” project type was changed to “Work Management” and various subcategories, such as:

• HR – Performance management and New employee
• Marketing – Email campaign and Event planning
• Legal – Document approval and IP Infringement
• Sales – Lead tracking and Sales pipeline

Each use case has its own fitting workflows and issue types. These can be adjusted later for more complex processes. For example, the “IP infringement” Legal template includes issue types “Claim”, “Task” and “Sub-task”, and a Simplified Workflow to transition between statuses freely. You’ll often find this type of workflow on agile boards.

Different Views

Software projects have Scrum and Kanban, Service projects have a Customer portal – and JWM projects now have five possible project views. The idea here is that because each team may work differently, it might need a different overview of its issues and tasks. One team requires a board, another a calendar, while a third one requires a roadmap layout.

The List view lets you work with issue fields as you would in a spreadsheet – change the content of the cells without going on an edit screen. While definitely practical for people used to working in Excel, it doesn’t allow you to include and edit all custom fields. Only a few types (single line, URLs, user type) are available to display at the moment.

The Board view resembles a Kanban from Software projects. However, you cannot set up multi-project boards, additional quick filters, or swimlanes. Still, if you are a fan of agile views – they are there.

You can also create, edit and view your issues in a Calendar view, which places tasks into days based on their due date. Even though it misses the option to choose another date field instead, it’s a good start. The next view, the Timeline view, also leverages the due field.

It resembles a good old Gannt-chart: create a line representing a Jira issue on a time range, similar to Plans in Advanced Roadmaps. Choose a Start Date and a Due date to display when the ticket is planned for. Connecting tasks via dependencies aren’t available at this point, but you can edit the issues as in any other view, making the roadmap especially useful for both scheduling and work with tasks themselves.

The last one is the Form view. Which enabled users to construct forms for e. g. customer support, with conditional fields, validators, and without needing to create too many custom fields.

It allows you to make a simple form that you can then share with anyone wanting to raise an issue in Jira (or from whom you simply need more information), without them having to understand how to work in it – the user just fills the fields and submits the form.

Creating issues is simple, custom views are handy, just like the integrated Automation for Jira features that make everyday JWM work easier. This enables business departments to join developers and operations squads already working in Jira, increasing effectiveness and avoiding siloing in the process. Please comment your thoughts on Jira Work Management!!