Put It Forward and Jira + Workfront Integration

[Farzaneh]

Has anyone used Put It Forward for Jira and Workfront Integration? If yes, what has your experience been like, from the beginning to to end (Discovery to Implementation), with the vendor and the product?

And what do you think about the pricing of the product/service?

How does the connection between the systems happen and how do the Workfront user roles come into play within the process? I am unable to find more than scratch of the surface of the app in the online references.

Thank you for sharing your knowledge with me.

[Madalyn_Destafney]

I haven't heard of Put it Forward - does it provide more capabilities than the native Jira integration?

[Farzaneh]

My understanding is that the native functionality provides a one way update from Workfront to Jira; it seems that Put it Forward provides additional and two way communication. Although Fusion provides that too but the pricing is considerable for Fusion.

[Madalyn_Destafney]

It's true that it's one-way in terms of the items need to be created in WF and pushed to Jira. But once created, it's two-way for updates/comments/status changes/etc. For example if someone makes a comment on a task in Jira that was created via WF, you'll see that update on the corresponding task in WF. 

[Farzaneh]

That is very helpful to know, Madalyn; I wish there was a demo that could show how the connection is created and how it works. 

We might be bale to work with that but the current desire is that the very first communication is initiated from Jira to Workfront projects (some and not all), and some data in Jira are custom created and coded so that might make things a bit more complicated. 

[Madalyn_Destafney]

Ah yup, that'll be the main limitation then, it doesn't work from Jira to WF. If you have Fusion, I'm sure you could do more with that between the two systems, but you're right it comes with a price tag. Check this out and other related links about the Jira integration.

[KatherineLa]

I can't comment on Put It Forward, but I can comment as someone currently building a custom Jira/Workfront integration with Fusion. If I knew everything that I know today back when we started building the Fusion part, I would not have moved the project forward and would have looked for a third-party solution. There is a significant and painful amount of technical complexity in the Jira API that makes it very difficult to work with in Fusion. 

[Madalyn_Destafney]

Good to know!

[Farzaneh]

Thank you for sharing your experience, Katherine; that is very helpful to know. 

[KIMBERLYREA]

I believe we've spoken about this before but I'd love to hear more of your lesson learns as we have a team starting this endeavor. 

[KatherineLa]

I can put a write-up together with some lessons, sure. 

[KatherineLa]

Funny enough, as I went to do my write-up of our implementation, I realized I HAVE come across Put It Forward before. This article on their site is part of what I send out to our internal teams every time one of them trips over "Workfront has a native connector!" and wants it implemented ASAP. 

https://www.putitforward.com/how-to-integrate-workfront-and-jira#toc-challengeswhenconnectingworkfro...