Based on this Atlassian Community answer and the documentation for "Move Issue" it appears that linked issues will not be affected when the issue type is changed. To ensure there are no problems, it would be prudent to verify the Screen Schemes are the same for your Story and Epic issue types, then create a test Epic with some linked Relates To and Issues in Epic issues and ensure moving the
There's two parts to this. It's absolutely correct that a sub-task should not be assigned to an Epic. A sub-task belongs to a parent, and hence belong to an Epic via that. It's absolutely a howling bug or flaw in JIRA that sub-tasks do not behave as though they belong to the same Epic as their parent. Yes, a few times I've scripted a field that
The epic is current so not closed. The content should remain fixed to it's planned for content for the current dev period but, because it is an epic used to collate general tasks/bug found across our tools internally, people have a tendency to raise an internal task and just link it to this current epic. As I say, I can inform people to stop
Hi @Fred van Beek. With regards your CSV import, With Epic, please use the epic link field as the parent/child fields are reserved for Task -> sub-task association. As you are bot the admin, make sure you can create and associate the issues from the Jira project’s create issue screen first else your import will potentially fail.
Copy the workflow, make your changes and then update the workflow scheme to sub in the new version of the workflow for the old one. Be sure to map the new workflow to the same issue types as they are currently mapped. And finally, be sure to publish the edited workflow scheme. Like • Chris Buzon likes this.
Jan 27, 2021. Technically, yes, but when you go to do it, you will find a warning not to. Heed that warning - it breaks a lot of things in interesting ways when Epics are not named "Epic". Atlassian do have an open and active development task on allowing it to be done, as Align needs it to be Feature instead of Epic as well, but until that is
7SRF. 315 226 349 48 391 322 329 232 23
jira change epic to task
