JIRA integration for Platform Bugs

Hi everyone! I wanted to share an example of how a monday.com and JIRA integration could be really useful for enabling seamless collaboration and communication between your developers that work out of JIRA and the teams that are not actively in JIRA. With this in mind, let’s take a look at this use case for bug reporting between Devs and non-Devs.

In this scenario, we have 3 audiences that need to communicate with each other on a daily basis. Our dev team which handles bugs, and then our management and partners team that works with the end users.

In order to collect data about a potential bug, we use a monday.com form which is embedded on our website. This is used by our partners to inform our CS team of any bugs they’re experiencing:

Platform%20Bugs

When this form is completed and submitted by the partner, we need a way to share this information with our developers who are working within JIRA. Our old process relied solely on email to communicate. Now, with the JIRA Integration, we can use the following integration to directly share the latest bug as an issue within JIRA:

In addition to creating issues in JIRA directly from our monday.com account for our devs to work out of, we will need to get daily updates from JIRA directly back to monday.com for each of these issues submitted. This allows the CS team to track the status of the issue without needing JIRA access. Using the automation below, we are able to rely on these updates to properly communicate back to the customer on the status of the issue at hand, keeping everyone in the loop:

This new process has optimized the way our teams can effectively collaborate on open bugs - a shift that has increased efficiency in dealing with bugs and in keeping our customers in the loop.

What are your thoughts on this use case? Would love to hear how others out there are using JIRA to track Platform Bugs and if you have any recommendations to share!

Aron

3 Likes

Hi, I’ve just setup the Jira integration and was hoping to utilise something similar but for our Product Development requests - I’ve setup to create an item in Jira when the status is changed to approved in Monday.com - but want the 2 way communcation to update the status back to Monday.com as the item progresses in Jira so was hoping using the ‘update this item’ option would work for this - however it looks like this needs to be setup for each individual item on the Monday board that you want to sync - is this correct - or is there a way to make this automatically sync?

Hi @ClareL! Great question - currently the two way sync is only for the following recipe:

Would you be able to reverse your workflow in terms of creating the items? We are looking to improve this integration and its recipes so if you have recipe ideas - feel free to post them here so we can take them into consideration :slight_smile:

Cheers!

Thanks for your reply, unfortunately for this scenario the reverse would not work as we are keen to manage items outside of Jira until a point we have decided to taken them forward for development.

Great to hear you are planning additions to the integration though as this could really embed Monday.com as platform for us and potentially allow us to utilise this for future plans. Currently I have setup an internal board with our companies PDR’s (product development requests) and this is a working board where we review and approve/ reject those we want to add to the roadmap. What I’d like to see on here is the ability to then create a user story in Jira from the accepted PDR’s but have the PDR board updated with Jira statuses so to remove any manually need to update on progress and give visibility to the internal stakeholder of progress.

A really usefully recipes would be:

  1. When a Status changes for an item to something, create an issue in this project and sync future changes from Jira

But also potentially expanding that to be able to select from groups - so it would allow me to create items into different projects in Jira or as different item types which are currently on one board in Monday:

  1. When a Status changes for an item in this group to something, create an issue in this project and sync future changes from Jira

Essentially its the 2 way syncing which is urgently missing - so your current recipes to include sync back from Jira options would be a great start.

Moving on from this it would be great to see more flexibility - so a way having if x field = x then create item in this project - so that we could cover wanting different Jira item types to be created - I.e some might need to be set as Epics or bugs rather than stories and to determine this from one board would be really useful.

Many Thanks

3 Likes

I’d like to add to what @ClareL has said, as we’d like to manage approval/denial of client requests and gate bug fixes based on urgency in Monday first, and only once the status changes in Monday does it get added to the Jira board.

However, additional to the two-way sync, I’m struggling to see how the Item/Pulse in Monday gets sent through with enough information to the Jira board - the Pulse Name/Title will come through as the “Summary” field in Jira. But what we’re trying to do is efficiently task up the requirements of a particular feature request first, and then once it’s been tasked up, change the status on Monday to Approved and have that shoot through to Jira.

Currently, without using Monday we’re using the “Description” in Jira to do this, but as our current workflow stands, there’s no way to gate which features are awaiting approval, versus have been successfully tasked but not approved, versus approved by the Product Manager. (Using Jira Cloud).

Monday could free up Developer time by reducing the amount of cross-checking needed when they receive a task, and give our Product Manager and Customer Success team an easy visual tool to enter requests and bugs and prioritise them efficiently.

1 Like

@ClareL @matt.easterbrook - this is great feedback! I really appreciate you both sharing how we can improve. I’m happy to push this forward to our team for consideration. If you come up with any other recipe ideas, feel free to post here on this thread :slight_smile:!

2 Likes

Did anything ever come of this? I’m still struggling with this issue. It basically makes the Jira integration pointless to use since you cannot mass change status, date, etc. from Monday… you can only do it from Jira.

1 Like

Hey @MK_Blackburn!

Thanks for following up here and checking in on this specific feature request for our Jira Integration. At the moment, I’m afraid that the recipe you’re looking for isn’t something that we offer at this time. Our developers are working continuously to strengthen the power of our integrations and I definitely hear how having that syncing ability work both ways would strengthen this integration.

I’ve passed this feedback again to our Autopilot Team and I’m hopeful that this can be implemented in the near future!

2 Way Syncing now available

This two way sync seems to be working for me with the exception of deletion. If I delete an issue in either Jira or Monday, it doesn’t update on the other system. Is this a known issue?

Monday-Jira integration is very buggy for me. The connector says that jira ticket can be created only when a row gets created in Monday. What I am noticing sporadically is that monday-jira integration gets triggered even on row update sometimes where it’s not expected.