Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,554,247
Community Members
 
Community Events
184
Community Groups

Differentiating Database Data by Client for Jira Cloud Plugin

Hi,

We want to release a Jira Cloud Plugin on Heroku. In this sense, we opened an application on Heroku and created a postgresql database. We used a single database in our developments. However, we need to keep the data of each customer separately while we are going live our application. For this process, we have separated data by Jira base URL, but there is no guarantee that this URL will not change.

Our current database structure;
 Table1
    column1
    column2
    ...
    baseUrl
 Table2
    column1
    column2
    ...
    baseUrl

In this structure, we separate the data of each customer according to the baseUrl. However, this solution is unreasonable and unreliable. Is there a way to keep each customer's data separate in the database? We could not find a definitive solution to the problem in our research. We wanted to get your thoughts on this.

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events