Uploaded image for project: 'Jira Software Server and Data Center'
  1. Jira Software Server and Data Center
  2. JSWSERVER-7203

Add the ability to create multiple Epic issue type in JIRA Software

    XMLWordPrintable

Details

    • 130
    • 25
    • Hide
      Atlassian Update – 3 September 2018

      Hi everyone,

      Thank you for your interest in this issue.

      While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status. The change requires an architecture change that may negatively affect other product areas.

      After careful review of the most pressing needs of our customers, we've decided to prioritize other areas of the Jira Server roadmap, some of them including your highly voted suggestions:

      In the recent Jira Server releases we have shipped some highly-voted features and improvements, including:

      • Filters and dashboards collaborative editing
      • Selectable delimiters in CSV export 
      • Microsoft SQL Server 2016 support 
      • iPv6 support
      • Faster Kanban boards
      • Refreshed projects and custom fields management pages in the admin's section 

      We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.

      To learn more on how you suggestions are reviewed, see our updated workflow for server feature suggestions.

      Kind regards,
      Katarzyna Derenda
      Product Manager, Jira Server

      Show
      Atlassian Update – 3 September 2018 Hi everyone, Thank you for your interest in this issue. While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status. The change requires an architecture change that may negatively affect other product areas. After careful review of the most pressing needs of our customers, we've decided to prioritize other areas of the Jira Server roadmap, some of them including your highly voted suggestions: Further performance and stability improvements Adding the "updated-by" JQL search query  JRASERVER-1973 Support for 4 byte characters in MySQL connection  JRASERVER-36135 Jira email notifications batching  JRASERVER-1369 Mobile app for Jira Server  JRASERVER-46149 Email notifications template editor available from the UI  JRASERVER-7266 Improved filter and dashboard management by Jira administrators  JRASERVER-15900  and  JRASERVER-41269 In the recent Jira Server releases we have shipped some highly-voted features and improvements, including: Filters and dashboards collaborative editing Selectable delimiters in CSV export  Microsoft SQL Server 2016 support  iPv6 support Faster Kanban boards Refreshed projects and custom fields management pages in the admin's section  We hope that you appreciate our candid and transparent communication. You can learn more about our  approach to highly voted server suggestions here . To learn more on how you suggestions are reviewed, see our  updated workflow for server feature suggestions . Kind regards, Katarzyna Derenda Product Manager, Jira Server
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      In current implementation of GreenHopper, a single Epic can support multiple projects as needed. This means that only a single Epic issue type is used for all boards available by default. And due to this configurations, users are not able to create a new Epic issue type, and have different boards to use different Epic.

      It will be great if GreenHopper allows users to create multiple Epic issue type, and configure the available boards to use specific Epic issue type as required.

      Sample use case:

      In our (and most likely other users) case we have a combination of hardware and software projects. The two project streams are loosely coupled. For the hardware side, the use of the word "Epic" would not feel really natural. Example: 2 Volts power rise within 10 nanoseconds is not an "Epic", it is a "Feature". On the other hand the software that drives the instrument can use the "Epic" terminology. Example: "Device drivers support power-on sequence and self-test of high-speed power card".

      Therefore I think it would be great if one could specify per configured board (Kanban or Scrum) which issue type should be considered the "Top Level Hierarchy".

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              afaisal Ahmad Faisal (Inactive)
              Votes:
              499 Vote for this issue
              Watchers:
              231 Start watching this issue

              Dates

                Created:
                Updated: