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!


How should i support 2 different hierarchies

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?

1 answer

0 votes
Deleted user Aug 21, 2020

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:

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.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events