Advanced Roadmaps Scheduling Based on Story Rank Rather Than Parent Epic Rank

[Kent Simpson]

I have been working to configure my first Advanced Roadmap plan the past few days, which has seemed promising, but am running into trouble with the auto-scheduling functionality. I am using the Roadmap with Basic View, and Hierachy from Epic to Story. Auto-scheduling does not appear to be considering epic rank, but only story rank when scheduling. 

Prerequisite work performed: 

    Created 3 epics, each with 4 stories within estimated at 5 days each. Epics were ranked top down on an epic Kanban board as higher, middle, lower, which is visible as Scope (rank) 1, 2, 3 on Roadmap. 

The stories in backlog 

Configuration:

    Issue sources:

        - Included 2 Sprint boards, each assigned to a different team (includes issues more

           granular than epics. i.e. stories, tasks, change requests)

        - Included 1 project (to pull the epics into Roadmap)

Has anyone seen similar behavior as above, or can recommend a configuration change to enable scheduling stories by their parent epic rank? As we are working with several teams, each team having their own Sprint board, we need to align teams to the product goal (which includes a prioritized epic backlog). 

Thank you for your help. Please let me know if I can elaborate further. 

[Daniel Ebers]

Hi @Kent Simpson

welcome to the Atlassian Community!

While I am unsure if you use a Server/Data Center or Cloud deployment I spotted Suggestions with Atlassian which could correspond with what you are seeing.

• Option to schedule by Epic rank rather than Story
  https://jira.atlassian.com/browse/JPOSERVER-1842
  https://jira.atlassian.com/browse/JSWCLOUD-19636

Could you please review the entries and state if it is was you are seeing?

Thanks in advance!

Cheers,
Daniel