Contact us for more information

Workfront-JIRA Integration

Features | The Problem | Preview

We designed the integration to be simple to configure and maintain through our Integration Hub administrator console. Unlike many other integration services, you do not need to be a developer to create queries and map out a workflow, which defeats the purpose of purchasing an integration product. The Workfront-JIRA Integration provides three easy to use mapping interfaces. One to identify what fields will be transferred between the source and destination system; one to map status options between the systems, and the third one to map priorities. You can be completely integrated in about 30 minutes.

Integration Features

  • Set implementation preferences through the Integration Hub admin console — no coding!
  • Replicate work from either Workfront or JIRA or both
  • Configure bi-directional synchronization preferences for paired work items
  • Start syncing work within 30 minutes of purchase
  • Project-by-project preferences to select the source system for replication (JIRA or Workfront)
  • Project-by-project preferences to replicate All Tasks/Issues or specific records (Status-Driven or Field-Driven)
  • Control which data points are replicated and synced from Workfront to JIRA, and from JIRA to Workfront
  • Control data points synced back from JIRA to Workfront, and vice versa
  • Map how Workfront status options translate to JIRA statuses
  • Map how Workfront priority values to JIRA priorities
  • Map how JIRA status options translate to Workfront statuse
  • Map how JIRA priority values to Workfront priorities
  • Map the JIRA issue types to be used for each Workfront object type (task or issue)
  • Control of replication/synchronization frequences
  • Select comment privacy options
  • Control what happens when JIRA issues are decomposed
  • Enable/disable replication of either tasks or issues

The Problem

The Solution

In Workfront, when a work item needs to be done by a developer or web deployment resource, that resource does not have visibility into the work they need to complete.The Workfront-JIRA Integration replicates the Workfront task or issue into a corresponding JIRA project and assigns or notifies the needed resource(s).
Workfront is used as the system to collect all hour entries and to produce progress and utilization reports. It is time consuming to move these manually and unrealistic to ask users to record time twice (and typically users in one system won't have access to the other).The Workfront-JIRA Integration synchronizes work logs, comments, and status back to the originating Workfront task or issue.
Workfront users need to know when development is slated to end, and when it finally does get completed. Currently they have no visibility.The Workfront-JIRA Integration can synchronize planned due dates and, upon completion, marks the Workfront work item Done as well.
Workfront users submit requests and typically view that request as a single work event; however, in JIRA those work items are typically broken down into smaller units. The Workfront users never have visibility into the subtasks or the estimated level of effort. Addtionally, the work logged to the JIRA subtasks aren't reported back to them.The Workfront-JIRA Integration supports the decomposition of JIRA work items. The effort, notes, and attachments on subtasks can be rolled up through their (paired-to-Workfront) parent task; or the subtasks can be replicated as subtasks to a Workfront task — the originating Workfront record must be a Task for this functionality.
In JIRA, when an issue needs to be completed by a Workfront resource, the Workfront resource does not have visibility into the work they need to complete.The Workfront-JIRA Integration replicates the JIRA task or issue into a corresponding Workfront project and assigns or notifies the needed resource(s).
A lot of organizations execute their development work in JIRA, but the effort of all this work need to be collected in Workfront to produce progress, utilization, and capitalization reports.The Workfront-JIRA Integration synchronizes work logs, comments, and status to the Workfront version of the JIRA issue. Hours entries, notes, and status changes are now reportable along with the other projects being planned solely in Workfront.

Integration Preview

The Workfront-JIRA Integration interface provides the ability to map which native data points will be replicated and synced between the two systems.

The Workfront-JIRA Integration automatically ingests native and custom status options from both systems to allow you to determine how status should be mapped.

The Workfront-JIRA Integration automatically ingests native and custom priority options from both systems to allow you to determine how priority values will sync.

The integration provides a preferences pane to allow you to control timing and other replication properties, including how they are broken down, replicated tasks should be treated; whether to display error messages in the Workfront updates feed for the work items, and what object type will be used to represent the source record in the destination system.