I’m currently trying to store data in a reliable way for my Atlassian Connect app.
I tried to add a “text” field in atlassian-connect.json to store my data in JSON format, but this type of field is limited to 255 characters, and there’s no way to add an unlimited text field from this file…
However, I found that it’s possible to create this type of field from the REST API, but it’s a pain to check if the field already exists to avoid adding it multiple times.
There’s also application properties but it comes with its own limitations, and I want to store my data per issue.
So how should I store my data, since there’s no obvious way to do it?
You actually listed all the options of storing data in Jira. The only other option is to store them in your own database.
Please vote for the multiline custom field support (the one defined in atlassian-connect.json): [ACJIRA-1661] - Ecosystem Jira
We will hopefully get it one day.
I checked and the current security level should allow a logged on user to vote for and watch the issue. Not sure why @quentin.bazin cannot vote for it when logged in. I tried it now and was able to access it as expected.
I finally decided to use my own database to store the data, but I definitely think entity properties (as mentioned by dzagorovsky) are the best way to achieve what you want. I plan to rework my plugin to use these properties instead of my database.