Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-9993

Closed/Completed Epics Not to Be Displayed in the Epic Link Field Suggestions

    • Hide
      Atlassian Status as at 11 February 2016

      This feature is now available for both JIRA Software Cloud and JIRA Software Server.
      The server release version is 7.1.0, please see the server release notes for further details.

      Kind regards,
      Martin
      JIRA Software

      Show
      Atlassian Status as at 11 February 2016 This feature is now available for both JIRA Software Cloud and JIRA Software Server. The server release version is 7.1.0, please see the server release notes for further details. Kind regards, Martin JIRA Software
    • 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.

      Currently, when you close an Epic/mark it as 'Done', it will still be displayed in the Epic Link field suggestions.

      It would be useful to be able to limit the list in the Epic Link field based on the Epic Status value of the existing Epics.

        1. e03-1.png
          e03-1.png
          98 kB
        2. e03-2.png
          e03-2.png
          100 kB
        3. e03-3.png
          e03-3.png
          96 kB
        4. Screen_Shot_2016-02-25_at_4_55_19_PM.jpg
          Screen_Shot_2016-02-25_at_4_55_19_PM.jpg
          85 kB
        5. System_info_-_JIRA.jpg
          System_info_-_JIRA.jpg
          14 kB

          Form Name

            [JSWSERVER-9993] Closed/Completed Epics Not to Be Displayed in the Epic Link Field Suggestions

            Dear Atlassian-Team,

            we've tested this thoroughly and the bug is still there.

            We are using Jira Data Center 8.20.10.

            Thank you in advance.

             

            Rainer Schmidt added a comment - Dear Atlassian-Team, we've tested this thoroughly and the bug is still there. We are using Jira Data Center 8.20.10. Thank you in advance.  

            Discovered today (for Server):

            The last status/option in the options in Epic Status (custom) field, will be taken as the "done" status for epics (so relevant for the Epic Link field)
            Even disabled status count.
            (We ran into this problem when migrating data from another instance with other status values)

            To unlock/lock the Epic Status field you can use following scripts:

            UNLOCK

            import com.atlassian.jira.component.ComponentAccessor
            import com.atlassian.jira.config.managedconfiguration.ManagedConfigurationItemService
            import com.atlassian.jira.issue.CustomFieldManager
             
            ManagedConfigurationItemService managedConfigurationItemService = ComponentAccessor.getComponent(ManagedConfigurationItemService)
            CustomFieldManager customFieldManager = ComponentAccessor.getCustomFieldManager()
             
            def cf = customFieldManager.getCustomFieldObjectByName('Epic Status')
             
            if (cf) {
                def mci = managedConfigurationItemService.getManagedCustomField(cf)
                if (mci) {
                    managedConfigurationItemService.removeManagedConfigurationItem(mci)
                }
            } 

            LOCK

            import com.atlassian.jira.component.ComponentAccessor
            import com.atlassian.jira.config.managedconfiguration.ConfigurationItemAccessLevel
            import com.atlassian.jira.config.managedconfiguration.ManagedConfigurationItemService
            import com.atlassian.jira.issue.CustomFieldManager
            ManagedConfigurationItemService managedConfigurationItemService = ComponentAccessor.getComponent(ManagedConfigurationItemService)
            CustomFieldManager customFieldManager = ComponentAccessor.getCustomFieldManager()
              
            def cf = customFieldManager.getCustomFieldObjectByName('Epic Status')
              
            if (cf) {
                def mci = managedConfigurationItemService.getManagedCustomField(cf)
                if (mci) {
                    def managedConfigurationItemBuilder = mci.newBuilder();
                    def updatedMci = managedConfigurationItemBuilder
                        .setManaged(true)
                        .setConfigurationItemAccessLevel(ConfigurationItemAccessLevel.LOCKED)
                        .build();
                    managedConfigurationItemService.updateManagedConfigurationItem(updatedMci);
                }
            } 

            Hope this helps

            Have a nice day everyone!

            Jakob Mayer-Maly added a comment - Discovered today (for Server): The last status/option in the options in Epic Status (custom) field, will be taken as the "done" status for epics (so relevant for the Epic Link field) Even disabled status count. (We ran into this problem when migrating data from another instance with other status values) To unlock/lock the Epic Status field you can use following scripts: UNLOCK import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.config.managedconfiguration.ManagedConfigurationItemService import com.atlassian.jira.issue.CustomFieldManager   ManagedConfigurationItemService managedConfigurationItemService = ComponentAccessor.getComponent(ManagedConfigurationItemService) CustomFieldManager customFieldManager = ComponentAccessor.getCustomFieldManager()   def cf = customFieldManager.getCustomFieldObjectByName( 'Epic Status' )   if (cf) {     def mci = managedConfigurationItemService.getManagedCustomField(cf)     if (mci) {         managedConfigurationItemService.removeManagedConfigurationItem(mci)     } } LOCK import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.config.managedconfiguration.ConfigurationItemAccessLevel import com.atlassian.jira.config.managedconfiguration.ManagedConfigurationItemService import com.atlassian.jira.issue.CustomFieldManager ManagedConfigurationItemService managedConfigurationItemService = ComponentAccessor.getComponent(ManagedConfigurationItemService) CustomFieldManager customFieldManager = ComponentAccessor.getCustomFieldManager()    def cf = customFieldManager.getCustomFieldObjectByName( 'Epic Status' )    if (cf) {     def mci = managedConfigurationItemService.getManagedCustomField(cf)     if (mci) {         def managedConfigurationItemBuilder = mci.newBuilder();         def updatedMci = managedConfigurationItemBuilder             .setManaged( true )             .setConfigurationItemAccessLevel(ConfigurationItemAccessLevel.LOCKED)             .build();         managedConfigurationItemService.updateManagedConfigurationItem(updatedMci);     } } Hope this helps Have a nice day everyone!

            @Henrik
            Its a shame that Jira does not use the resolution value of "Done" but rather uses the status "Done". This means I need to change my Epic workflow just to fix absurdly annoying issue.

            Please put out a real fix for Jira Cloud!!!!!

            Alexander Pinkerton added a comment - @Henrik Its a shame that Jira does not use the resolution value of "Done" but rather uses the status "Done". This means I need to change my Epic workflow just to fix absurdly annoying issue. Please put out a real fix for Jira Cloud!!!!!

            Henrik added a comment -

            You need to make sure the field "Epic Status" is set to Done. Then it will disappear from the list.

            Henrik added a comment - You need to make sure the field "Epic Status" is set to Done. Then it will disappear from the list.

            It's not fixed. When I choose when I don't choose 'Show done epics' in the Epic Link, done epics are still shown. Please take care of it

            Наталя Кічало added a comment - It's not fixed. When I choose when I don't choose 'Show done epics' in the Epic Link, done epics are still shown. Please take care of it

            We really need this feature working.. we are struggling that this says it is fixed, but it really isn't.  

            Sandra Fuchs added a comment - We really need this feature working.. we are struggling that this says it is fixed, but it really isn't.  

            +1 really frustrating not fixed in Cloud

            Catherine Borrie added a comment - +1 really frustrating not fixed in Cloud

            Hi Team , Is this fix available for Jira data center Version Atlassian Jira Project Management Software (v8.20.1) we are currently facing an issue with the same 

            Jennifer Lobo added a comment - Hi Team , Is this fix available for Jira data center Version Atlassian Jira  Project Management Software  (v8.20.1) we are currently facing an issue with the same 

            The Cloud version has a separate project, but the related ticket (if it exists) isn't linked here

            Piotr Janik added a comment - The Cloud version has a separate project, but the related ticket (if it exists) isn't linked here

            wimpers added a comment -

            +1 not fixed in cloud

            wimpers added a comment - +1 not fixed in cloud

              Unassigned Unassigned
              dchua Daryl Chuah (Inactive)
              Votes:
              136 Vote for this issue
              Watchers:
              147 Start watching this issue

                Created:
                Updated:
                Resolved: