JIRA INTEGRATION

[#1]

as in the meantime most of the Development companies use JIRA it would be great to provide an "out of the box" seemless integration with Jira that makes it easy to

> map one Jira issue to one Workfront task or

> map several Jira issues to one Workfront task

Fields that should be exchanged are mainly

• progress
• planned hours
• actual hours

This allows to use the excellent Controlling capabilities, the gant chart, the reports ... of Workfront

and the strong Workflow capabilities of JIRA

[#2]

It'd be awesome if that integration included comments (notes) as well.

[#3]

We have implemented a Workfront to JIRA integration that makes use of JIRA Webhooks. If interested I can provide more details. We make use of JIRA Webhooks and Workfront is the system of record. Our implementation provides for bidirectional comments.

[#4]

Anything you have to share would be great, Paul!

[#5]

Paul, I'm interested in your integration as well.

[#6]

Paul, I would be interested as well - so if you have anything to share that would be great!

[#7]

I apologize for the delay in responding. We have built a JIRA/Workfront API integration and have been using it with excellent results for more than a year. This will be a lengthy post. At the time we initially created the JIRA integration we needed to interface with the technical side of our business ( that exclusively uses JIRA ) and also to take advantage of Kanban boards in JIRA. I will provide an example of what we did to interface with our JIRA software developers.

We needed to add a couple of new Workfront status's so we created a new Workfront group and named it Example_Agile ( I will use example rather than our real names ). We added the following status's to the group: New, In Progress, Complete, Blocked and Parking Lot. A blocked status indicates something that is blocked and we have an estimated time to resolve the blocker. A parking lot status represents a blocker and we are unable to obtain an estimated time to resolve.

Next the Workfront Administrator creates a Workfront team and assigns members to the team. Our team name has a name of Organization_TeamName_AGILE.

When a Workfront Project is created it must be assigned to the group Example_Agile ( this is necessary to be able to see your desires status's in the project ).

Our integration maps Workfront Tasks to JIRA Issues.

When a project manager creates an AGILE Task in Workfront, they provide a Task Name a Description and they must assign the task to the Agile Team. The can also input an optional planned hours.

We created a custom Workfront form named "JIRA Connector" The custom form contains a single textbox named JIRA Issue ID.

Our API integration software runs every 5 minutes. The software searches for all tasks assigned to an agile team that does not have the custom form "JIRA Connector" attached. If the agile task does not have the form the API integration adds it and then creates a new JIRA issue. After the JIRA issue is created the JIRA issue id is written back to the Workfront JIRA Connector form.

When the API integration creates the JIRA issue it uses the Workfront Task name and description and also includes a convenience url that links back to the associated Workfront task. Workfront is our system of record for all time entry. Our API integration takes advantage of JIRA webhooks so its a near real-time update when changes are made in JIRA.Comments in Workfront and JIRA are bidirectional. Whenever a JIRA issue is moved from one column to another on the Kanban board the status is updated in Workfront

When the the JIRA issue is created we add two JIRA labels - one is the agile team name and the other is the Worfront project number. This allows us to setup a JIRA Kanban board thats specific to a project and an agile team.

Our integration supports both waterfall and agile within Workfront.

We have implemented our API integration using C# .Net.