Inherited workflows for issue types

Peter Gillard-Moss

I want to understand how I can setup a Jira project so that it can work with different types which inherit a super workflow.

As an example imagine I have an Events project. We do Weddings, Mitzvahs, Birthdays, Funerals and Corporate Events.

Each of these require their own workflow because they are slightly different (we have a Book Celebrant status for weddings and a Book Clown status for birthdays).

Each type would then have its own kanban board to manage the event.

However, the Events Manager needs to oversee all events and wants a single kanban board for a high level view.

They want to see Request, Booked, Planned, Delivered, Invoiced, Paid.

Problem is, some of these status' might be the same (all events have Booked) but their status' for Planned might be different (e.g. Booked maps to Booked Clown).

How would you go about achieving this?

 

Trudy P Claspill

Hello @Peter Gillard-Moss 

Welcome to the Atlassian community.

I agree with @John Funk that you should use a Company Managed Software project. That will better suit your needs for multiple boards. Only a Jira Administrator will be able to create the project 

A Jira Admin can create a custom workflow for each issue type. The workflows get associated to the issue type through a Workflow Scheme, which will then need to be associated to the project.

You can create and save Filters for each of the event/issue types and then create a kanban board for each based on the saved filters 

In the board created with the project the project admin will need to map all of the statuses of the individual workflows to columns on the board. The names of the columns on that board can be generic (Request, Booked, Planned, etc.). Each column can have multiple statuses mapped to it. So if the event/issue workflows have unique Booked Something statuses, those can all be mapped to the generic Booked column on the board used by the EM.