I am using a generalPages module in my app and would like to add an entity_property_equal_to condition to it. Unfortunately, this fails on app install with the following message:
Installation failed. The app includes a Page module with an unsupported condition (entity_property_equal_to).
I have integrated my application to Atlassian Connect Express a long time back and now suddenly, while uploading the application to ACE, I am getting the below error. I am unable to understand it’s a failure.
Error:
“Installation failed. The app includes a web-fragment condition (entity_property_equal_to) with invalid parameters (This entity type is not valid, you provided ‘project’)”
The descriptor file contains modules->webItems and modules->webPanels which has the condition:
{
“condition”: “entity_property_equal_to”,
“params”: {
“entity”: “project”,
“propertyKey”: “xxxxxxxx”,
“value”: “true”
}
}
Below is an example of legacy web panel entry for our Signature app that uses the same entity property condition. This format is accepted by current version of ACE.
It looks very similar to yours… maybe check the conditions wrapping array.
Thanks for the quick reply.
Yes, there is difference in the “conditions” tab from the script you have mentioned here.
I did make the relevant changes but still the error persists.
Error :
Installation failed. The app includes a web fragment condition (entity_property_equal_to) with invalid parameters (This entity type is not valid, you provided ‘project’).
What is the location of the panel? If it is not within an issue Jira may not have a context project to evaluate. Maybe try changing location to an issue panel as a test…
This is the condition:
{
“condition”: “entity_property_equal_to”,
“params”: {
“entity”: “project”,
“propertyKey”: “XXXX”,
“value”: “true”
}
}
which is present at 2 locations :
jira.project.sidebar.navigation in modules->webItems
atl.jira.view.issue.left.context in modules->webPanel
There is no “objectName” in your params element. I believe that needs to be set to the name of the element within your custom stored json propertyKey. At least for our page we needed it.
Yes, I agree that we don’t have ‘objectName’ as one of the parameters in the condition. But it should not affect as in the document objectName is mentioned under optional parameter. It’s no where written that objectName is a required parameter for ‘entity_property_equal_to’.