What this article covers:
- An example use case of a Trello-Jira workflow
- Creating your flow
- Mapping statuses and fields
- Mapping custom fields
- A video of the flow in action
We've launched an evolution of our product, so some of the terminology and guidance in this article might be a bit out of date, and we're working hard to update it. You can learn more about our new workflow offering here, brush up on the new terminology here, and find out how to build your first workflow here.
An example use case of a Trello-Jira workflow
In this example, a website revamp project involves marketers working in Trello and developers working Jira. Here's what their respective projects look like.
Creating your flow
Starting your flow is just a matter of following our easy step-by-step process. Here it is in action.
Mapping statuses and fields
Mapping is how we match up elements from both tools with each other. For example, while a due date in Trello is synced by default with a dude date in Jira, you might need to map Trello lists to Jira statuses.
Mapping custom fields
If you have a Team, Company, or Enterprise plan, you can sync custom fields in Trello. In this workflow, we're using this feature to create "Priority" and "Sprint End Date" fields in Trello, which are then synced to Jira.
The flow in action
Now that the flow has been created, teams in Trello and Jira can work together with greater visibility. Here's what that looks like in action:
With Unito, cross-functional project workflows become seamless. You never have to argue about which tool to use or worry about tasks getting left behind. If you want to know how Unito can enhance your workflow, please reach out to us!