A few months ago, our team began evaluating whether or not the project management tool we were using was bringing enough value to our marketing organization to justify its price. Unfortunately, by the time that we began this investigation, our renewal date was just about a month away, so we were on the fast track.
One of the first tools we explored—for a multitude of different reasons—was Atlassian’s JIRA cloud platform. For those of you who are unfamiliar, JIRA is a tool originally created for software development and bug tracking that was recently expanded to make it more friendly for what they call “Business Team” use cases. Our marketing team was interested in using JIRA’s business project management capabilities, and after some initial exploration, JIRA checked off many of our major requirements.
Unfortunately, JIRA was missing one core feature that our teams required—the ability to templatize subtasks depending on the type of issue that was submitted into the system. The lack of this feature makes sense if you’re aware of JIRA’s origins, but unfortunately, it was a major blocker for our team. Luckily JIRA has a very robust API, and we here at TIBCO know a little bit about APIs.
So, what did we do?
In JIRA, every issue type is associated with a workflow, and every step of a workflow can trigger different activities—one of which is calling a webhook. Every time an issue is created in our JIRA system, we call a webhook that points to an end point within a TIBCO product called TIBCO Cloud Integration. TIBCO Cloud Integration allows you to quickly and easily model, create, test, and deploy APIs, without writing a single line of code.
We call a webhook and point to an end point in TIBCO Cloud Integration, where we have a microflow running. Within the microflow, we have all of the different issue types defined, and within each issue type, we’ve outlined the subtasks that need to be affiliated with it. Once the issue type name passed from JIRA matches with an issue type name in TIBCO Cloud Integration, the product triggers a bulk issue create API call to JIRA that then creates all of the configured child subtasks of the original issue.
It’s no secret that marketing tools can eat up a ton of budget, so it’s important to get the most bang from your buck. With almost all modern marketing solutions, if you want new features, you’re at the mercy of the product’s roadmap. However, by pairing TIBCO Cloud Integration with the increasingly large number of exposed APIs many of today’s tools offer, you can maximize your investment by building in the exact functionality you need (and on your own schedule!) We did it ourselves using TIBCO Cloud Integration and saved over $50,000! Why wouldn’t you? Start your free 30-day trial today!