How should i support 2 different hierarchies

[Randy]

We have several projects already using advanced roadmaps, and the global settings look like:

• initiative ...
• epic ...
• story (defaults)
• sub-task (defaults)

Now we have other teams using R4J and requirements based projects and they have something like this (not in the the plan tool):

• Customer Requirement / New Feature
  • (with possibly several levels of customer requirements tree here)
• Functional Requirement / Non-functional Requirement
  • (again possibly 1+ levels)
• Task
• Sub Task

We also have "Test", "Test Execution", ... (all from XRAY) that should be represented in the hierarchy somewhere.

I dont want to break existing "stry" type projects, but want to allow the requirements projects to use the planning features in roadmaps.

Any thought on the best way to do this?

[Deleted user]

The hierarchy of themes/initiatieves/epic/stories is bases on the duration of that item:

"While an epic is something you might complete in a month or a quarter, initiatives are often completed in multiple quarters to a year." Quote from this article: https://www.atlassian.com/agile/project-management/epics-stories-themes

If you customer requirement is broke into several functional requirements, then you can create an initiative for the customer requirements with underlying epics for the functional requirements.

My suggestion for Test and Test execution is to make that part of your scrumboard by adding columns if you want every item to be tested (and consider this extra work when estimating it).
If you want to do all the testing at the end of the project you can create a separate task-ticket for it.