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. 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. I have defined a Jira Project with a number of Initiatives. Under each Initiative, there is a number of Epics that originate from different Jira Projects. Under each Epic, there are tasks that come from different Jira Projects. I am struggling to find a query that will dynamically list all of the Epics and Tasks that are added to the Initiatives. Answer accepted. To update this Question, today as of March 4th, 2019, you CAN convert a Task or any type of issue into a sub-task, just by clicking the 3 dots () icon to the far right of the issue title and selecting MOVE. In the Move issue screen, you must select the sub-task (you got to have it enabled or added as an issue type in the 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. 1 Answer. you don't want to add a sub-task in your epic. The epic is used as a "link", you can specify which epic your features (jiras) belongs to in issue edit screen. The features themselves does not need to be a sub-task of the epic. QA will still be able to create sub-task off your features. Here are documentation from Atlassian https PtLATR0. How to create an epic that should contain stories which should contain tasks using python-jira. PAT Jun 28, 2020. Writing a script in python using python-jira library to convert nested dictionary to jira issues where the epic should have stories and the stories should have tasks where the details for each are in a nested dictionary. Typically for SW OOB you will see something like: Epic, Story, New Feature, Improvement, Bug, Task or similar. Epic is unique from all other issue types. Stories, New Features, Improvements and Task are all more or less equivalent but obviously have different meanings. They can all have Sub-Tasks and they can all be linked to each other. 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. Change Epic to Story: What happens to the Stories and tasks that fall under it. New Jira user here. We are currently under a reorg and management has identified some changes. One is that specific Epic should be converted to a story. However, it is a number of Stories and tasks beneath it. If the issue type is changed will the association to the You can also link to other Jira applications like Jira Software or Confluence. For example, you might want to link an incident to Jira Software when a second or third line support member needs to work on a fix. To link an incident record to a task in another project: View the incident record. Select the more menu (). Select Link. Adding subtasks to an epic upon its transition. Osama Al-Areky Oct 19, 2023. Hello, I would like to automate the addition of new sub tasks to an epic once this epic is transitioned, for example: an epic is transitioned from to do, to on going, then auomatically subtasks are created and added to it. I tried different ways to create a rule, but

jira convert task to epic