Jira plugin error parent link only for premium users

CloudQuery Plugins
1

I’m also getting an error on the Jira plugin when I try to see the parent.

"customfield_10018": {
  "showField": false,
  "nonEditableReason": {
    "reason": "PLUGIN_LICENSE_ERROR",
    "message": "The Parent Link is only available to Jira Premium users."
  },
  "hasEpicLinkFieldDependency": false
}

I thought you guys switched to a per row pricing here?

2

That looks like an error from JIRA, actually.

3

Oh shoot, thanks!
I created this issue, but… perhaps you’re right. That’s a weird issue. I can’t find it in Jira’s docs at all that they block that.

PLUGIN_LICENSE_ERROR is the thing that throws me off; that doesn’t seem like a Jira message. But you’re right, I found this:

"nonEditableReason": {  
    "reason": "PLUGIN_LICENSE_ERROR",
    "message": "Portfolio for Jira must be licensed for the Parent Link to be available."
}

So after upgrading, I’m still not seeing the parent info. I get the “use epic link instead” message, but there’s no epic link data. Those fields are null:

customfield_10010: null
customfield_10014: null
customfield_10015: null
customfield_10016: null
customfield_10017: null
customfield_10018: {3}
showField: false
nonEditableReason: {2}
reason: EPIC_LINK_SHOULD_BE_USED
message: To set an epic as the parent, use the epic link instead
hasEpicLinkFieldDependency: false

Something isn’t right with the plugin, because when I call the REST endpoint it gives me for an issue, for example: https://devgrid-inc.atlassian.net/rest/api/2/issue/10837, it returns the parent info:

"parent": {
    "id": "10547",
    "key": "DEV-487",
    "self": "https://devgrid-inc.atlassian.net/rest/api/2/issue/10547",
    "fields": {
        "summary": "Person Views",
        "status": {
            "self": "https://devgrid-inc.atlassian.net/rest/api/2/status/10001",
            "description": "",
            "iconUrl": "https://devgrid-inc.atlassian.net/",
            "name": "In Development",
            "id": "10001",
            "statusCategory": {
                "self": "https://devgrid-inc.atlassian.net/rest/api/2/statuscategory/4",
                "id": 4,
                "key": "indeterminate",
                "colorName": "yellow",
                "name": "In Progress"
            }
        },
        "priority": {
            "self": "https://devgrid-inc.atlassian.net/rest/api/2/priority/3",
            "iconUrl": "https://devgrid-inc.atlassian.net/images/icons/priorities/medium.svg",
            "name": "Medium",
            "id": "3"
        },
        "issuetype": {
            "self": "https://devgrid-inc.atlassian.net/rest/api/2/issuetype/10002",
            "id": "10002",
            "description": "Epics track collections of related bugs, stories, and tasks.",
            "iconUrl": "https://devgrid-inc.atlassian.net/rest/api/2/universal_avatar/view/type/issuetype/avatar/10307?size=medium",
            "name": "Epic",
            "subtask": false,
            "avatarId": 10307,
            "entityId": "39dd09bf-7c70-45eb-8577-c515496616d8",
            "hierarchyLevel": 1
        }
    }
}

The custom fields are all null as expected; the plugin just isn’t capturing the parent object.

4

Could you open an issue for this?