Can't configure the 'Jira Issues' Macro in Confluence

[Claudiu Guiman]

Hi,
I’m trying to set up a known issues section in my plugin’s wiki page, but I can’t set up the Jira extension.
The URL I’m using is https://issues.jenkins-ci.org/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?jqlQuery=project+%3D+JENKINS+AND+status+in+%28Open%2C+%22In+Progress%22%2C+Reopened%2C+Resolved%2C+Verified%2C+%22In+Review%22%29+AND+component+%3D+azure-vm-agents-plugin&tempMax=1000  , but the macro returns : “jiraissues: Unable to determine if sort should be enabled.”

Is this some known issue or am I providing the wrong URL?

Thanks,

Claudiu

[Daniel Beck]

> On 15.12.2016, at 23:50, 'Claudiu Guiman' via Jenkins Developers <jenkin...@googlegroups.com> wrote:
>
> Is this some known issue or am I providing the wrong URL?

AFAIR this is an incompatibility between Confluence and Jira versions and it's been broken since we upgraded Jira a while back.

[Claudiu Guiman]

Hi,
Is there any workaround or any plan to fix it?

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Fmsgid%2Fjenkinsci-dev%2F98D33658-D3E2-4C72-90B4-9F702BA82680%2540beckweb.net&data=02%7C01%7Cclguiman%40microsoft.com%7C36970cffc12b46dd551f08d4253f7cb7%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636174401979294122&sdata=6RhaJbV1jdHIQAnO9xlu5eRm9vsb8OvmGX%2BzHFPMks4%3D&reserved=0.
For more options, visit https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgroups.google.com%2Fd%2Foptout&data=02%7C01%7Cclguiman%40microsoft.com%7C36970cffc12b46dd551f08d4253f7cb7%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636174401979294122&sdata=5U2b0%2BbotUD1dXPbTowHRTEdq%2BBAQLDWX8dTssc0%2F5w%3D&reserved=0.

[Daniel Beck]

> On 16.12.2016, at 00:10, 'Claudiu Guiman' via Jenkins Developers <jenkin...@googlegroups.com> wrote:
>
> Is there any workaround or any plan to fix it?

I don't think so.

You can track this issue here: https://issues.jenkins-ci.org/browse/INFRA-575
And the Confluence upgrade here: https://issues.jenkins-ci.org/browse/INFRA-325

As you can see, not exactly high on the priority list.