You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I would like to ask you a question about requirement organization in R4J/Jira. First, let me explain briefly the issue for a better understaind.
We have a project in R4J. In the past, we have been using the tree view to organize requirements. Each folder corresponds to a component in our system. As an example:
During the requirement writting, we identify a new requirement 4. This relates to component A (folder A) and B (folder B). I know that there are several solution to fix that kind of interactions. For example, by defining a custom field "Component" and using the search view in Jira to find requirements per component.
The point is that for workers who are not really familiar with Jira, the tree view is a way better to find requirements than JQL queries or the basic search. Therefore, my question would be: is it possible to include a requirement on two folders? Something like:
If you have any comment or recommendation I would really appreciate.
I'm Edmer from EaseSolutions, vendor of R4J plugin.
Right now, it isn’t possible to add the same issue in multiple folders on the same tree. Moving forward, we already have an existing request in our internal backlog to support multiple instances of issue in the tree.
If you want to get notified when this feature will be released, we'd be glad to help you when you raise a ticket at our service desk portal or follow our Marketplace page by clicking on "watch app" under Resources to be notified about new releases.
(I'm thinking about a generic answer, so not sure whether it adresses your need).
Provided there is a limited number as a whole, maybe you could create a quick filter (in a board) or a JQL filter per component ? Filters are stored JQL queries, they could even be a good starting point for the workers to become familiar with more advanced Jira features.