JIRA Pipeline Stories - WMS Trello Card Connection

1 Introduction
2 Purpose
3 Product/projects involved
4 Map of statuses vs lists
5 Instructions
6 General
7 Statuses, lists, and columns
- 7.1 Statuses (Jira)
- 7.2 Columns (Jira)
- 7.3 Lists (Trello)
8 Unito Settings
- 8.1 Flow direction
- 8.2 Rules created
- 8.3 Field mapping

Introduction

Unito is a no-code two-way integration solution that can connect two apps and automate workflows. In this case, we are connecting a Jira project with a Trello board.

Purpose

Integrate Jira and Trello through Unito to mirror Jira tickets in Trello.

Product/projects involved

Product	Name	Link

Product	Name	Link
Jira Instance	Indigina	https://bigdigit.atlassian.net/
Project - Jira	Pipeline	https://bigdigit.atlassian.net/jira/software/c/projects/SPIP/boards/102
Board - Jira	Business Requirements (Kanban Board)	https://bigdigit.atlassian.net/jira/software/c/projects/SPIP/boards/102
Board - Trello	Prioritized Function	https://trello.com/b/6cleh8RZ

Map of statuses vs lists

Status - Jira	List - Trello	Comments

Status - Jira	List - Trello	Comments
Ticket created	Ticket created
Prioritized business narrative	Prioritized Business Narrative
Development Initial Scoping	Development Initial Scoping
Write Requirements	Write Requirements
Global Review	Global Review
Detailed Requirements	Detailed Requirements
Verifying Specification	Verifying Specification
Create Dev Tickets	Create Dev Tickets
Dev Level of Effort	Dev Level of Effort
Dev Plan Allocate	Dev Plan Allocate
Development/QA	Development/QA
UAT	UAT
	Release to Production	No needed in Jira
Completed	Completed
Cancelled		No needed in Trello

Instructions

If the item is created in Trello, make sure to select the label WMS. Otherwise, the ticket will not be created in Jira and the custom field Product will not be selected as WMS.

Label: WMS

General

If the names of the lists in Trello are changed, the synchronization will break up.
If there is a Status in Jira that does not have a corresponding List in Trello, the Status will not be reflected on the card on Trello.
If you want a particular Status not to be displayed on the Trello board, you just have to make sure that the Trello board does not have a List for that particular Status .
Synchronization is set up so that everything that is created and modified in Jira is reflected in Trello. This means that whatever is created, modified, archived, or deleted in Trello will not be reflected in Jira.
If the card created in Trello through synchronization is deleted, this will not affect the ticket originally created in Jira.
Changes made in Trello cards may take some time to be reflected in the ticket in Jira, and vice versa. Be patient.
When creating a card in Trello, please note that the title will be automatically updated with the Jira ticket number.

Statuses, lists, and columns

Statuses (Jira)

An issue's status indicates its current place in the project's workflow.

SPIP Business Workflow for Stories

Columns (Jira)

Columns in a Kanban board are used to map with status. Each column on the board represents a different stage of the workflow.

Kanban Board - Business Requirements

Lists (Trello)

A list is a collection of vertically-arranged cards. They may represent a collection of ideas, things to remember, or different stages of a workflow.

Trello Board - Prioritized Functions

Jira & Trello Connection

Every time the status of a ticket in Jira changes, its corresponding card in Trello will also be updated accordingly. Make sure the status names in Jira and the list names in Trello match.
The column names of the boars in Jira are not related to the connection between Jira and Trello.

Unito Settings

Flow direction

Two-way sync

Rules created

Sync from Jira to Trello

Sync from Trello to Jira

Field mapping

Sync between issues and cards