We are changing from having Initiatives only in a separate Initiatives project to adding Initiatives directly to projects. Now however, when I select "Create Issues in this Epic" for new Issue view, the Initiative issue is available.
The hierarchy has not changed for months and is setup correctly for this. I cannot figure out whether
1) this has always been the behavior, but we never added Initiatives as an Issue type to the projects before,
2) or whether also consolidating the workflows so that Initiatives, Epics and Stories share the same workflow? or
3) Initiatives sharing screen schemes with Tasks and Stories might be at issue
Or some combination of the above?
Hi @Pat Ryan ,
Thanks for pointing this one out, and and this behavior is a bit buggy, as you should not be able to link an issue as both a child and parent of an epic.
I created the following two Bug Reports for some follow up action, noting you are on the Cloud Platform so only the first link is relevant to your use case and I was not able to locate any adverse fallout on the Cloud platform but I wanted to make sure the info was here for both platforms incase anyone else finds this post looking the an answer for the server platform BUG as there are some minor differences in the behavior on each platform and and additional Bug occurs Server side when this reciprocal linking occurs:
But at this time manual review of the issues via JQL to look for initiatives with an epic link and manual correction is the only workaround. Make sure to add yourself as a watcher on the Bug to get updates.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event