Skip to content

Jira Service Desk doesn't start with JasperListener / need relaxedPath with correct version comp #288

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 6, 2019

Conversation

thonixx
Copy link
Contributor

@thonixx thonixx commented Mar 6, 2019

Pull Request (PR) description

Pull request of #260 (issue #259) wanted to prevent JasperListener to be
activated for Service Desk. Version comp condition can't be fulfilled as
Jira and Service Desk have different version numbers.

Therefore JasperListener gets added to the server.xml anyway with Service Desk. To get Service Desk working we need to adapt the condition to not match when we run Jira Service Desk.

Also relaxedPath options only needed from Jira version >v7.12.1 and Service Desk

(According to https://confluence.atlassian.com/jirakb/changing-server-xml-to-handle-requests-with-special-characters-958453799.html)

We need to have relaxedPathChars and relaxedQueryChars set according to
the FAQ page of Atlassian with Jira version greater than 7.12.1 and
apparently Service Desk.

This Pull Request (PR) fixes the following issues

Issue does not exist (yet), relates to issue #259 which doesn't work. Also relaxedPath should only be configured with the correct versions and for Service Desk.

thonixx added 2 commits March 6, 2019 15:54
Pull request of #260 (issue #259) wanted to prevent JasperListener to be
activated for Service Desk. Version comp condition can't be fulfilled as
Jira and Service Desk have different version numbers.
…e Desk

According to
https://confluence.atlassian.com/jirakb/changing-server-xml-to-handle-requests-with-special-characters-958453799.html
we need to have relaxedPathChars and relaxedQueryChars set according to
the FAQ page of Atlassian with Jira version greater than 7.12.1 and
apparently Service Desk.
@thonixx thonixx changed the title Jira Service Desk doesn't start with JasperListener on Jira Service Desk doesn't start with JasperListener / need relaxedPath with correct version comp Mar 6, 2019
@bastelfreak bastelfreak added the bug Something isn't working label Mar 6, 2019
@bastelfreak
Copy link
Member

thanks for the fix @thonixx !

@bastelfreak bastelfreak merged commit 84a81e7 into voxpupuli:master Mar 6, 2019
@fabiogermann fabiogermann mentioned this pull request Mar 7, 2019
@zogot
Copy link

zogot commented Jun 12, 2019

Any chance to get this released? It's been a few months since this got merged, but it would be valuable for those that are upgrading to version 8 of jira, of which the arguments are required.

@bastelfreak
Copy link
Member

hey @zogot, a new release depends on #298 and I currently don't have the time to look into this. Please let us know if you would like to help out. If so, you can have a look at the failed travis jobs and investigate why postgres isn't working.

@dhoppe dhoppe mentioned this pull request May 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants