Where to store project specific configuration element?

[Yves Martin]

 Hello

For an add-on design, I am looking for the best/proper way to store per project configuration entries or "properties":

First option: Opensymfony PropertySet:

• https://developer.atlassian.com/server/jira/platform/architecture-overview/#propertyset
• https://docs.atlassian.com/software/jira/docs/api/7.6.1/com/atlassian/jira/project/ProjectPropertiesManager.html

Second option: entity properties and its REST API

• https://developer.atlassian.com/server/jira/platform/entity-properties/
• Located at /rest/api/2/project/{projectIdOrKey}/properties

Third option: add-on specific storage with ActiveObjects

• https://marketplace.atlassian.com/apps/1217709/project-properties-for-jira?hosting=server&tab=overview
• https://bitbucket.org/scmenthusiast/jira-project-properties-plugin/wiki/Home

When browsing "propertyentry" in dabase, it is possible to find only one project PropertySet "firstIssueCreated", but not project entity properties. And even atlassian products may not be consistent, as project specific properties are stored as "jira.properties" and I have not found what API has created other bamboo specific project properties for which entity_name is project key (and asking myself what happens when renaming project key?)

172491 | Project | 13960 | firstIssueCreated | 1
172343 | APROJECTKEY | 1 | bamboo.release.config.24674 | 5
172344 | APROJECTKEY | 1 | bamboo.release.config.defaults | 5
172639 | jira.properties | 1 | applinks.local.APROJECTKEY.jira_project.linked.entities | 5

With so many possibilities, I am lost and still have opened questions:

• where second-option project properties are stored?
• what are benefits / drawbacks of each option and which one would you recommend?

[Venkat Prasad]

Thank you Yves for the analysis and feedback.

Though we keep everything in Jira database, here are couple of things I think to manage own AO Store/SQL queries instead of Core Jira API/Storage i.e.

• Using own AO Store/SQL queries I will have more flexibility/control to track more information like, author, last updated, etc
• JQL Search Functions

[Yves Martin]

I agree your plugin has added value thanks to "JQL Search Functions", but I think it would have been possible to use Atlassian entity properties storage for both user project properties values and metadata - and so with reuse of REST API.

[Venkat Prasad]

I agree Yves, thank you for heads-up. I will make sure to analyze core features for my upcoming plugins. :)

[Yves Martin]

I can already submit a partial answer about "entity properties".

Even if its storage is JSON text in table "entity_property", it seems to be designed for both JavaScript support and plugin usage thanks to ProjectPropertyService: https://docs.atlassian.com/software/jira/docs/api/7.11.0/com/atlassian/jira/bc/project/property/ProjectPropertyService.html