Select the search field in the navigation bar and select View all issues. Click the Project filter, and select the project you want to migrate from. (If you're looking at the Advanced mode, you'll need to select Basic) In the top-right corner, select more () > Bulk change all.

In general, you can locate issues which have an Epic Link applied (as long as this is a Classic Project): Action: Issue Updated. Condition: Advanced Compare Condition - { {issue.Epic Link}} (first value) does not equal (condition) - then leave "second value" as Empty. ^ Then, utilise: Branches to locate the related/linked issues.

Epics and Features are higher level containers. User Stories and Tasks are more sub-level components. Epics can DIRECTLY be broken into User Stories/Tasks (aka backlog items) Epics IDEALLY need to be broken down into Features. Features can be broken down into User Stories / Tasks / Backlog Items. These tasks / stories are what fit into SPRINTS.
Edit the cloned story or issue to taste. 3. move using . move OR within the issue view, edit the Epic link by "clicking in" and then selecting from a list of Epics from the dropdown box. 4. you will find in your new Epic (Epic 2), the cloned issue associated with it. Hope this helps :) Reply.
As the automation for sub-task is triggered when a Task is created, it considers the Task as the issue. Hence, when we say, { {issue.parent.epic.summary}}, the automation is unable to understand as the Task has Epic as the parent. Update the automation with ' { {issue.epic.summary}} : { {issue.summary}} : Task-1'. It is working as expected for me.
To promote a feature: On the features page, select Promote f rom the More Actions menu on the toolbar (top-right of the page). Select Feature as an object, and then select a PI and a program. Under Parent, select the feature which you want to promote to a parent epic. Under Child, select the check boxes of the features which will be child
A "workaround": create a dummy Story. move the Epic with its child issues. select for the Epic the new type "Story" and for the child issues select "Sub-Task", which forces you to select a Story. choose the dummy Story. execute the move operation. your Epic is a Story and its child Tasks are Sub-Tasks of the dummy. ZBuXxzs.
  • 2866mavps9.pages.dev/261
  • 2866mavps9.pages.dev/117
  • 2866mavps9.pages.dev/76
  • 2866mavps9.pages.dev/986
  • 2866mavps9.pages.dev/616
  • 2866mavps9.pages.dev/70
  • 2866mavps9.pages.dev/302
  • 2866mavps9.pages.dev/131
  • 2866mavps9.pages.dev/646
  • 2866mavps9.pages.dev/612
  • 2866mavps9.pages.dev/640
  • 2866mavps9.pages.dev/227
  • 2866mavps9.pages.dev/433
  • 2866mavps9.pages.dev/399
  • 2866mavps9.pages.dev/25

    • jira convert task to epic