How do we replicate a custom table that stores data at the component level in Jira cloud

[Kiran Joshi]

Hi Jira experts!

We are looking into moving our on-prem Jira instance to the cloud. We currently have a custom table where we store Approvers and Business Owners at the components level. When a new ticket is created these custom fields get auto-populated with data from this table. This allows us to email only the approvers at the component level when a ticket is ready for approval (instead of e-mailing all approvers on the project).  Since it doesn't sound like we can continue to use this custom table in Jira Cloud, I was wondering if anyone had suggestions about how we could replicate this functionality if we move to the cloud.

Thanks so much!!

[Andy Heinzer]

Hi Kiran,

I see that you are looking to migrate from Jira Server to Jira Cloud and are looking to some means to replicate the functionality you have here.  In Jira server, you can customize the database as this is something you operate on the backend.  But the same is not true of Jira Cloud.  You actually don't have access or control of the database in Jira Cloud.

My thought would be to try to leverage the Automation in Jira Cloud to try to replicate the behavior here.  All Jira Cloud sites have automation built into them.   Whereas with Jira Server or Jira Data Center, this is an additional app/add-on.

With automation you can trigger specific changes to an issue based on factor in the issue, like a specific field value.  Granted I don't know how complex this might be to setup in your case.  As I don't know just how large your existing table is and how much data is both stored there and what kinds of data is then populated to these issues. 

But that said, I would recommend checking out getting started with Jira Cloud automation as a means to try to build some rules to replicate this functionality.

I hope this helps.

Andy

[Kiran Joshi]

Hi Andy,

Thanks so much for your answer! I did take a look at Automation in Jira Cloud , and it looks like that would help with sending the e-mail notifications when we need to. However, I don't see a way that would allow us to store the component level data. In terms of complexity, we have some projects with over 100 components and each component has two or three approvers. We have one table that stores all of this information (project, component, approvers, business owners).

Thanks!

Kiran