Back to Mavenlink.com Blog Tour Status

JIRA Integration Overview

OVERVIEW

Mavenlink’s JIRA integration makes it possible for organizations to automatically synchronize project information between Mavenlink and JIRA or JIRA Agile. Create JIRA issues from Mavenlink and improve issue tracking within JIRA, enabling reporting and issue resolution. Project status, logged time, and user communication can be transferred between Mavenlink and JIRA on a configurable schedule.

BENEFITS

The Mavenlink-JIRA integration allows project teams to perform project activities in the application of their choice, while relying on either application to accurately present project information. This is useful for software development teams that use JIRA for managing engineering stories and sprints, yet also need a unified project delivery solution like Mavenlink with broader project management, resource management, and business intelligence capabilities.

Key Benefits Include:

  • Improved communication between team members using different systems
  • Increased efficiency by avoiding redundant data entry through bidirectional communication between the two systems
  • Improved reliability on the accuracy of information in each system

FUNCTIONAL CAPABILITIES 

Mapping Scenarios

  • Map Mavenlink Project to JIRA Project
  • Issues in JIRA become Tasks in Mavenlink and vice versa 
  • Sub-Tasks in JIRA become nested Tasks in Mavenlink

  • Map Mavenlink Project to JIRA RapidBoard
  • Sprints in JIRA become top level Tasks in Mavenlink
  • Issues (User stories, Bugs etc.) in JIRA become nested Tasks in Mavenlink
  • Sub-tasks in Jira become nested Sub-Tasks in Mavenlink
  • Backlog Issues come over under a Backlog task in Mavenlink

Actions

  • Create and update Tasks and Sub-Tasks / Issues and Stories
  • Create and update Comments
  • Create time entries in Mavenlink from time logged in JIRA. Note: Mavenlink time is booked on a per day basis and no time entry over 24 hours can be booked for a day. This means that JIRA time entries larger than 24 hours will not come over to Mavenlink (e.g. for a single JIRA time entry of '2 weeks', only 24 hours will come over to Mavenlink). 
  • Capture the Epic, Fixed Versions and JIRA Issue ID in custom fields of the corresponding Mavenlink Task.
  • Configurable mappings for different Task types (milestones, deliverables, issues, etc.) and Statuses (not started, started, completed). 

CONFIGURABLE OPTIONS

  • Select the frequency and schedule of your integration synchronization
  • Select whether to send time entries from JIRA to Mavenlink
  • Select whether to include JIRA subtasks
  • Select whether to include the backlog
  • Map specific field value pairs for certain fields (e.g. Task Statuses) between the two systems
  • Map Mavenlink Users to JIRA Users
  • Apply custom filters using Mavenlink API filters and JIRA JQL

AVAILABILITY AND ACCESS

The JIRA integration is available to Mavenlink Premier accounts as a Professional Services configuration. To get started, speak with your Account Executive or Client Success Manager, or email support@mavenlink.com. Once the integration has been activated by a Solutions Engineer, the integration will be administrator-configurable using the Mavenlink Integrations web-based user interface.

The integration requires that the JIRA account is configured to allow remote API connections. This can be enabled by a JIRA administrator in General Settings.

The integration requires that the JIRA instance be accessible through the web. We can connect to both JIRA Cloud and JIRA Server. The integration was built using JIRA Agile 6.7.12 (https://docs.atlassian.com/jira-software/REST/6.7.12/) so any JIRA version supporting this API is supported by our integration.

FIELD MAPPINGS 

TIME ENTRIES

Mavenlink Field

Direction

JIRA Field

Date Performed

<=

Date Started

Time

<= 

Time Spent

Billable

<=  

N/A (user configurable)

Notes

<=  

Comment

Estimate

<=

Original Estimate

 

COMMENTS

Mavenlink Field

Direction

JIRA Field

User

<=>

User

Message

<=>

Message

 

SPRINTS

Mavenlink Field

Direction

JIRA Field

Title

<=>

Summary

Start Date

<=>

Start Date

Due Date

<=>

End Date

State

<=

State (Past, Active, Future)

Custom Field

<=

Epic

Custom Field

<=

Fixed Versions

Custom Field

<=

JIRA Issue ID

 

ISSUES

Mavenlink Field

Direction

JIRA Field

Title

<=>

Summary

Description

<=>

Description

Time Estimate

<=>

Original Estimate*

Due Date

<=>

Due Date

State

<=

Status

Assignee

<=>

Assignee

Custom Field

<=

Epic

Custom Field

<=

Fixed Versions

Custom Field

<=

JIRA Issue ID

 * To pass estimates, time tracking has to be enabled and configured for your JIRA project. For more information, refer to your JIRA documentation: Configuring time tracking. When not configured properly, the following JIRA error will be thrown: "Field 'timetracking' cannot be set. It is not on the appropriate screen, or unknown"

Note: Objects of the above types are created and updated. Deletes are not processed at this time.

Created on

Can't find what you're looking for?

Live Chat Submit a Ticket