R4J - How to organize requirements

[Felipe Castillo Ruiz]

Hi all,

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:

• Folder A (component A)-> Requirement 1
• Folder B (component B)-> Requirement 2
• Folder C (component C)-> Requirement 3.

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:

• Folder A (component A)-> Requirement 1, 4
• Folder B (component B)-> Requirement 2, 4
• Folder C (component C)-> Requirement 3.

If you have any comment or recommendation I would really appreciate.

[Edmer John Sarmiento]

Hi @Felipe Castillo Ruiz

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.

Best regards,

Edmer

[Felipe Castillo Ruiz]

Hi Edmer,

thank you for the updates. Do you have a ticket number so that I can track also the new feature status?

[Edmer John Sarmiento]

Hi @Felipe Castillo Ruiz,

Currently, there's no plan yet when this feature will be added. You may check our product roadmap when this feature will be included in our upcoming feature release.

Best regards,

Edmer

[Nicolas Gondard]

(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.