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

Epic Still Show on the Suggested List on the Epic Link despite Being Closed and Marked as Done

      Epic Still Show on the Suggested List on the Epic Link despite Being Closed and Marked as Done.

      Expected Behavior

      No longer appear in the suggested list when the Epic is being marked as done

      Current Behavior

      Despite the Epic is being marked as done on the Agile board. Creating a new issue and clicking on the Epic Link, it will still suggested the closed Epic.

      Tested closing the Epic via issue view still having the same result

          Form Name

            [JSWSERVER-11362] Epic Still Show on the Suggested List on the Epic Link despite Being Closed and Marked as Done

            Jira team... JSWSERVER-9993 is about something else.  This issue is still present in the currently live cloud version and affects the "Issue Link" dropdown in the preview (both modal and detail views exhibit this behavior) of an issue on a Kanban board.  If you click through to the full issue view, then the Epic Link field works as described in JSWSERVER-9993.

             

            That issue being fixed does not imply this one is.  Please re-open and fix the issue.

            Daniel Bingham added a comment - Jira team...  JSWSERVER-9993 is about something else.  This issue is still present in the currently live cloud version and affects the "Issue Link" dropdown in the preview (both modal and detail views exhibit this behavior) of an issue on a Kanban board.  If you click through to the full issue view, then the Epic Link field works as described in JSWSERVER-9993 .   That issue being fixed does not imply this one is.  Please re-open and fix the issue.

            Simon added a comment -

            I also still experience this bug with Jira v7.12.3. Do we have to re-open this bug again?

            Simon added a comment - I also still experience this bug with Jira v7.12.3. Do we have to re-open this bug again?

            This is not resolved, is it? Why is this bug closed? 

            Deleted Account (Inactive) added a comment - This is not resolved, is it? Why is this bug closed? 

            Resolving this issue and linking it to the canonical issue describing this improvement.

            Regards,
            JIRA Agile team

            Michael Tokar added a comment - Resolving this issue and linking it to the canonical issue describing this improvement. Regards, JIRA Agile team

            We're reopening this issue, it is not the expected behaviour and agree that an epic that is Marked as Done should not be included in the Suggestions part of the drop-down list.
            We will also investigate further if there are use-cases to include the epic in the lower section of the list.

            Regards,
            JIRA Agile

            Martin (Inactive) added a comment - We're reopening this issue, it is not the expected behaviour and agree that an epic that is Marked as Done should not be included in the Suggestions part of the drop-down list. We will also investigate further if there are use-cases to include the epic in the lower section of the list. Regards, JIRA Agile

            This was created after service desk confirmed it's a bug. I agree, should not be closed with won't fix!

            Hannes Gänser added a comment - This was created after service desk confirmed it's a bug. I agree, should not be closed with won't fix!

            Why was this closed? It happens as described and makes it very hard for our team to correctly categorize.

            Zachary Drummond added a comment - Why was this closed? It happens as described and makes it very hard for our team to correctly categorize.

              Unassigned Unassigned
              rgee Richie Gee (Inactive)
              Affected customers:
              3 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated:
                Resolved: