In Advanced Roadmaps (Data Center) I can't move 2 orphaned Epics up under their parent Initiatives

[Steve Josue]

In Advanced Roadmaps (Data Center) I can't move 2 orphaned Epics (TMS-3711 and TMS-3622 in the attachment) up under their parent Initiative (JIRA 9.1.0). I've included a screenshot. The orphaned Epics, as shown, will go under "any initiative above" except its rightful parent "TMS-3247". When we attempt to move it under Initiative TMS-3247 it stays shaded red (no-go). I think I have asked this before but am trying again with a screenshot as I am completely out of ideas. Something is wrong with that Initiative. I have re-imported it in from our Prod system again thinking it was corrupt somehow. We are using Adv Roadmaps as a POC to leadership to show its potential and can't have this happening.

Any help/suggestions are greatly appreciated.

Best,

-Steve Josu

[Mark Segall]

Hi @Steve Josue - This is odd.  I would try a couple things:

1. Do you have issue level security employed on that project?  Perhaps that particular issue has a security level that makes it view-only.
2. Did you also try dragging it into another issue where status = Backlog?   Perhaps there's some type of workflow property preventing linking while the parent is in the Backlog?
3. Have you tried adding the Parent Link field to the Epic screen for the TMS project and seeing if you can manually set TMS-3247 within the Epic itself?

[Steve Josue]

Hi Thank you for your reply:

1) I'll have to figure out how to do this.

2) Yes, I tried all the available states, no change. Again, all the other Initiatives have no issues and lots of children. This initiative has none (but should have the two I referenced).

3) Oh yes, I tried that. But no matter what I type in the parent link field it persists with "no match found" ....as if it wasn't ever looking in the first place. I will look into your #1 item.

Best,

-Steve

[Mark Segall]

One other thing to try... I've never seen it myself, but maybe the issue type field is corrupt on that particular issue for some reason.  Are you able to change the issue type to something else and change it back?

[Steve Josue]

I can try that!

[Steve Josue]

Great idea didn't fix, I am at a complete loss here.

[Mark Segall]

This one may be an issue to raise with Atlassian support unfortunately.  I can't think of any reason why this would happen with one issue.  

As a workaround, maybe you can just clone that issue and re-link all the children to the clone.

[Steve Josue]

I actually re-exported the Initiative from Production and Imported into our TEST system with no change. Crazy! I was thinking sometimes Atlassian monitors this board (I think) and was hoping maybe they could chime in. I'll try to generate a ticket. Thanks for all your help on this!