Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Issue with "Show in Issue Navigator" in R4J: invalid JQL syntax


The "Show in Issue Navigator" option in R4J does not handle special characters properly.

Here's an example.

I have a requirements tree path that looks like "Foo&Bar/Framus". When I right click it and select "Show in Issue Navigator", the issue search JQL generated is:

issue in requirementsPath("\"Foo&Bar\"/Framus")

Jira doesn't like this at all. It says:

Invalid project name received in the path. Please submit with the valid project name.

I have to manually edit out all of the escapes, and then the following JQL actually works correctly:

issue in requirementsPath("Foo&Bar/Framus")

So all of the escapes are not only unnecessary, they are actually in error. Every time I use this feature on my project I have to hand-edit the JQL to fix it. Pretty annoying.

1 comment

Bernhard Doleschel _Ease Solutions_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Nov 23, 2022 • edited

Hello @mbratch ,

I´m Bernhard from Ease Solutions, the vendor of R4J. Thanks for reporting this annoying issue.

We´ve identified this bug already in the past, there is a fix in place with R4J version 4.11, released middle of October 2022. The problem occurred due to unhandled special characters in the project name. For a workaround I can recommend to remove characters like  \ / : * ? " < > |

Please contact your system admin to update your system.

If there any more questions we can help you with, please raise a ticket at our friendly service desk team:

Have a great day,

Bernhard from Ease Solutions


Log in or Sign up to comment