I've reached out a few times on this ticket as well as email but haven't received a response on appropriate steps to follow for a bug that was not properly resolved.  Re-opening and assigning to ddortch@atlassian.com.  Repasting notes regarding why.

This ticket was closed indicating it was a duplicate of 1071.  I don't think this is the case.  Byrd, Darryl, Emily and I all met to discuss ranking issues that were occurring in the roadmaps.  Kyle advised that two tickets would need to be filed for the issues.  That was 1071 and this one.  1071 has been fixed but the issue presented in this ticket still exists.  When viewing work items in a nested view, the children are being displayed in order of ID as opposed to their rank.  Kyle mentioned that the nested view in the roadmap should match the nested view in the backlog.  For example, Feature by Epic (nested view) in Roadmap should rank by Epic backlog and features under epic by Program PI rank.  Can we please get this one re-opened and looked into?

ddortch@atlassian.com I made some notes on 5/19 about this issue not being resolved and seeing if we can get this re-opened.  I'm not familiar with the correct process to go about doing this.  Are you able to help?

This ticket was closed indicating it was a duplicate of 1071.  I don't think this is the case.  Byrd, Darryl, Emily and I all met to discuss ranking issues that were occurring in the roadmaps.  Kyle advised that two tickets would need to be filed for the issues.  That was 1071 and this one.  1071 has been fixed but the issue presented in this ticket still exists.  When viewing work items in a nested view, the children are being displayed in order of ID as opposed to their rank.  Kyle mentioned that the nested view in the roadmap should match the nested view in the backlog.  For example, Feature by Epic (nested view) should rank by Epic backlog and features under epic by Program PI rank.  Can we please get this one re-opened and looked into?

This is a duplicate of ticket 1071 which is currently in work. please follow that ticket. 

rgibbs@atlassian.com I will reach out to PM to get them to add the complete "fix results" so dev will have a clear picture identifying what needs to be fixed and what the acceptance criteria's are.

kbyrd@atlassian.com - Can you please review this defect and add the expected results for this issue along with updating the acceptance criteria on the internal defect for Suppor?

Kind Regards,

DD

Hey Darryl - According to what kbyrd@atlassian.com told us, the nested view should match the parent-child backlog view.  So for this example where we are talking about features being nested under epics, it should match how features are displayed under epics in the Epic backlog view.  I also believe the issue is applicable to all nested view, this was just the example of which we were viewing.

The expected behavior described in this comment is also how the supporting documentation was updated by the Content team.