Hi,
We are migrating a Connect app to Forge.
We’re going to start testing the app on the Forge platform, but we have a few questions.
1. Dashboard gadget.
To indicate that the Forge app will replace the Connect app, we specify this in the manifest.yml file using “app.connect.key”
So far, so OK; but in our case, the Connect app has several Dashboard Items:
....
"jiraDashboardItems": [
{
"key" : "xxx",
"name": {
"value" : ....
}
....
},
{
"key" : "yyy",
"name": {
"value" : ....
}
....
}
....
]
....
that we have migrated to Forge:
....
jira:dashboardGadget:
- key: aaa
title: ....
....
- key: bbb
title: ....
....
....
a) How do we specify which Forge gadget replaces each Connect dashboard item? Would it be through a “key”?
b) If so, would it be advisable for all migrated Forge modules to have the same “key” as in Connect?
c) When Forge gadgets replace Connect gadgets, will they be able to access the properties that the Connect dashboard items already had configured?
2. App properties.
Our Connect app stores a small amount of information as app property. The Forge app will collect this information and store it in its storage.
Will the Forge app be able to access this information? In other words, will it be able to use the service?
GET /rest/atlassian-connect/1/addons/{addonKey}/properties/{propertyKey}
Currently, it returns to us:
{
code: 404,
message: {
"statusCode":404,
"message":"App with key does not exist."
}
}
3. Test license.
We verify the license using “active” in the “context” (context.license.active !== true), as described here.
We have observed that there are more fields:
{
active: true,
subscriptionEndDate: null,
trialEndDate: null,
....
}
In the case of type “trial”, would it be necessary to check if the “trialEndDate” date has been exceeded?
If so, where can we see the format in which these parameters will be received?
Thank you very much in advance.
Regards.