Book Image

Jira Work Management for Business Teams

By : John Funk
Book Image

Jira Work Management for Business Teams

By: John Funk

Overview of this book

Jira Work Management (JWM) is the newest project management tool from Atlassian, replacing Atlassian's previous product, Jira Core Cloud. While Jira Software focuses on development groups, JWM is specifically targeted toward business teams in your organization, such as human resources, accounting, legal, and marketing, enabling these functional groups to manage and enhance their work, as well as stay connected with their company's developers and other technical groups. This book helps you to explore Jira project templates and work creation and guides you in modifying a board, workflow, and associated schemes. Jira Work Management for Business Teams takes a hands-on approach to JWM implementation and associated processes that will help you get up and running with Jira and make you productive in no time. As you explore the toolset, you'll find out how to create reports, forms, and dashboards. The book also shows you how to manage screens, field layouts, and administer your JWM projects effectively. Finally, you'll get to grips with the basics of creating automation rules and the most popular use cases. By the end of this Jira book, you'll be able to build and manage your own Jira Work Management projects and make basic project-related adjustments to achieve optimal productivity.
Table of Contents (15 chapters)
Section 1: Jira Work Management Basics
Section 2: Enhancing Your JWM Project
Section 3: Administering Jira Work Management Projects

Common automation use cases

Although we have already discussed automation templates and the automation library, it will help to look at some common use cases specifically. These use cases have come about based on frequent questions in the Atlassian Community user support environment and previous Atlassian support requests.

So, let's take a look at some of the most common ones:

  • Keeping parent issues and subtasks in sync: As many of the JWM project templates include subtasks in the initially created issue type scheme, auto-transition of the parent tasks can be based on the movement of the subtasks. In other words, when the first subtask moves to In Progress, the automation rule will move the parent into the In Progress status. The same can happen when the final open subtask is closed, as we move the parent issue to Done, as shown in Figure 10.11:

Figure 10.11 – A parent and child automation task rule

  • Assigning an issue to a user...