Mantis to Jira Automation

[Holly]

We're a small company of 16.  The developers love Mantis, The design, marketing, web admin love Jira.  One is for bugs, the other handles both.  The company will not move wholly to Jira, unfortunately.  Is there any way to automate integration between them to make everyone happy?  I have seen something about webhooks, but nothing definitive...  CUrrently we have a big enhancement project that would be best managed in Jira...

[Bill Sheboy · Accepted solution]

Hi @Holly 

You ask about automating the integration between Jira cloud and the Mantis defect management tool.  Please consider more specific details about what information you want exchanged between systems, direction, timing, etc.  That will help you evaluate approaches, and may help the community offer ideas.

In addition to webhooks, the REST API and automation rules are features to consider.

Please review the previous posts about Mantis to see if others ideas resonate with what you are trying to do:  https://community.atlassian.com/t5/forums/searchpage/tab/message?q=mantis&collapse_discussion=true&search_type=thread

One more thing to investigate is the Atlassian marketplace to see if there are any third-party vendor add-ons to help.  Those usually have additional costs per user.  https://marketplace.atlassian.com/

Best regards,

Bill

[Holly]

Thank you for taking the time.  We've done a quick fix approach at this point due to lack of buy in from the development team, who unfortunately prefer Mantis.  Hopefully we can convince the business owner that Jira is the way to go.  Unfortunately they had a go before I came on board, and had a bad experience.  I have certs in Scrum and heaps of experience in Jira, but it hasn't mattered.  Bad experience is bad experience... I love jira, and it's silly for such a small company to have two tools, so hopefully we can approach it right and make the switch.

[Bill Sheboy]

Hi Holly,

Thanks for that update.  As you proceed, consider people and teams work in different ways, and so tools that help one group may not help another.  Remember that tools like JIRA are just tools; they are not meant to change how a team works but instead support it.

Also consider observing and discussing what about these tools is helping and what is causing concerns.  That knowledge will help you as you try to mitigate or resolve the concerns and get more value out of the things that help.  I have found doing this helped me when there are multiple tools like JIRA and Mantis with overlapping and supporting responsibilities, and people seem entrenched in their desire to use one versus another tool.

Best regards,

Bill

[Holly]

Preaching to the choir mate.  But Mantis is a bug tracker, not a feature planner  I've been in IT for 30 years, SW Dev for 20 of those, in three different countries using all sorts of different tools.  You also need to use the right tool.  And that is not happening, and it hasn't been up for discussion.  I am coaching the team on how to approach.  Been there more times than I can count.  And I have adapted tools to get them to work as well, but Mantis has less adaptibility than Jira..  And for a company of 16 employeesw, with a global reach, when Jira can do both, it's not an efficient use of resources especially in these crazy days.