Learn how to use Wrike and Unito to triage development requests directly to Jira, GitHub, GitLab, or Bitbucket.
The benefits of triaging development requests through a project management tool
IT and dev teams are bombarded by requests via email, chat, meetings and cubicle drive-bys. Someone has to capture all of these requests, sort through them, remove duplicates, and re-file them into the issue tracking tool of the team, which is Jira more often than not. If this overhead wasn’t enough, the requester often doesn’t have (or want) access to the tracking tool for updates.
This guide will show you how to best use Unito to channel all requests made from Wrike directly into Jira, while keeping communications opens between the Wrike request and the resulting Jira issue.
How to build a development triage project in Jira
1) Sync your Jira project(s) into Wrike
Identify every Jira project you would like to send requests to. For each of those projects, create a flow in Unito, and add a rule that will exclude all existing Jira issues. Since Unito syncs in both directions, this rule will prevent any existing Jira issue from becoming a new Wrike task, while letting new Wrike task requests become Jira issues. We recommend you type in a dummy Jira label called WRIKE-REQUEST, in the label rule field shown below.
Once you save your flow, Unito will create an empty folder in Wrike for each of your Jira projects. Any new task added to these folders will become a Jira issue.
2) Create Wrike request forms
Wrike request forms automatically create and normalize new tasks in a designated folder. You can read more about them in Wrike’s help centere.
Create a new form for each of the Jira projects you would like to send requests to, selecting the empty Jira folders created above as the destination. Define the standard set of questions for new requests.
3) Submit new requests
Let your colleagues in Wrike know of the new request form(s), and submit-at-will!
Each new request will become a Wrike task, which Unito will sync into a Jira issue. From that point on, any change made to the task or issue will be converted over. The IT or dev team can push the issue through their standard internal process directly from Jira. This means Wrike users can track, comment and get answers on the request without ever leaving Wrike.
Recommended Unito settings
Try out these settings to get the most out of your workflows:
-
Set the default issue type so new requests become the right type of issue in Jira. You could also create a new request issue type in Jira specifically for this.
-
Create a custom workflow in Wrike to map to your Jira workflow, and see project progress live.
-
Map your Jira priorities to Wrike importance, so the importance of new requests is passed on to Jira.