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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,457,853
Community Members
 
Community Events
176
Community Groups

R4J: How to Manually Modify requirementsPath of an issue when you can't navigate to it in R4J Tree

I have some issues in R4J that seem to have gotten "lost."  They don't show up on the requirements tree, though the Jira tickets still exist.  I cannot re-add them to the tree because it says they're already there, but I cannot find them on the tree because it says they're not there.

I'm guessing that they somehow ended up with a requirementsPath tag that is not a valid part of the tree - but how do I modify that without being able to access them through the tree?  It doesn't seem like its an accessible jira field.

1 answer

1 accepted

0 votes
Answer accepted

Hello @Ryan Arata

I'm Angelica from EaseSolutions, vendor of R4J plugin. I'm not sure which version of R4J you're using, but first thing to try is the "Move issues within own project tree" feature.

Right click on any folder in your project tree and select "Add existing issues" then select the source "Move issues within own project tree". You can use a JQL query to indicate the Jira issue that seems to have been lost.

moveissues.PNG

Something else that could be done is executing the integrity checker to Check Folder & Issue References.

If none of these help, we'd be glad to help you at our service desk portal for further investigation.

Best regards,
Angelica

Thanks Angelica, this worked for me!

Sounds great! Happy to help. :)

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events