Sep 24, 2019. Hi @carmella_smith. You could try this : proj = jira.search_issues ("'Epic Link' is not EMPTY and project = 'your project (s)'") It will list all issue that belong to an epic. After that with a loop you can access to the epic issue number. The code below give you access to the epic link issue number.

Before you begin. Make sure you have the Move Issues and Create Issues project permissions. Your Jira administrator can help assign any needed permissions. If you want to move multiple issues between projects at the same time, check out the Editing multiple issues at the same time page.
Likewise, if you are moving child issue(s) and they have a linked epic, then you will get a warning to tell you that the child issues will lose their epic link. Example screenshots: (when moving epics without their children issues) (when moving children issues without their epic(s)) We are closing this ticket as resolved. 1 - Use a template. When starting a new Jira ticket, developers might get a form of writer’s block. Even after creating a ticket, necessary information may be missing. By using a checklist template (like the one below) you can avoid this problem. Here is a template in markdown I use to create scope for new Jira tickets: How to enable Jira cloud integration. Admins follow these steps to enable integration: From the sidebar, go to Admin and select the Integrations tab. In Jira, you'll have an option to Enable the integration. If a connection was made previously or if the integration was already enabled, you'll have the option to Manage the enabled integration.

Answer accepted. @Satyajit Baral - As stated by the Atlassian team, I am sure that you already know that a child (i.e. one EPIC) can only have one parent/One parent can have multiple children (Jira) - For example. Initiative A (created using Advanced Roadmap hierarchy setup) Please see the attached picture.

Thank you for you response and for the information. I should have been more clear, while I do need the Cancel resolution to be accessible all across my Jira projects, I actually need help with the Next-Gen software settings. I understand the process for the adding a resolution for a Classic software Jira project.
lS78AP7.
  • we91sq3ibe.pages.dev/70
  • we91sq3ibe.pages.dev/138
  • we91sq3ibe.pages.dev/7
  • we91sq3ibe.pages.dev/246
  • we91sq3ibe.pages.dev/316
  • we91sq3ibe.pages.dev/330
  • we91sq3ibe.pages.dev/271
  • we91sq3ibe.pages.dev/119
  • we91sq3ibe.pages.dev/396

    • jira convert ticket to epic