To do so, enter the subtask's detailed view, and then click on More > Convert to issue. Depending on the JIRA version, it might be displayed an ellypsis [] button instead of the More button. Once all subtasks had been converted into tasks, enter the task that you'd like to convert into an epic and click on More > Move.
Steps (check out the attached for details) Trigger = Issue created [Note: this would be for one of the child issues.] Use a Lookup issues command to find the parent of the issue. Create a variable to store the key of the parent (e.g., { {myParent}}) Use Lookup issues commands to find each possible sibling.
Unless otherwise noted, the timeline view in Jira Software is the same for both company-managed and team-managed projects. The timeline is where you can create, manage, and visualize work from a board. Timelines are useful for planning large pieces of work several weeks or months in advance and planning large groups of stories.
Connect JIRA with Asana via Zapier. Click the Use this Zap button below. Follow the prompts to sign up for a Zapier account, or sign in if you already have one. Connect Asana and Jira to Zapier. Follow the steps to set up the Zapier automation, known as a Zap. Test out your new Jira Zap.

In this #Atlassian #Jira video you are going to learn how to make an #Epic a child of another issue type. Epics are usually the highest level you can go out

From Features. Set "Mapping" to "On" and you will see the Epics listed in the right panel. Drag and drop the feature to the Epic you'd like to assign. Open the feature item. Click "Link to" button under "All Links" tab. Set "Link Type" to "Parent" and enter the ID of the Epic you'd like to assign.

Just paste your Jira link on a Confluence page and it will automatically drop a dynamic Jira issue link on your Confluence page. Once you publish the page, the link will display the issue ID and title, issue category (epic, task, etc.), and issue status in the workflow (to do, in progress, done, etc.).

.