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

XMLWordPrintable

      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

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

            Bugfix Automation Bot made changes -
            Minimum Version New: 6.03

            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.

            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?

            Deleted Account (Inactive) added a comment -

            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? 
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2851355 ] New: JAC Bug Workflow v3 [ 2932792 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2544031 ] New: JAC Bug Workflow v2 [ 2851355 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1550881 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2544031 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: affects-server fixme New: affects-cloud affects-server fixme
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: fixme New: affects-server fixme
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 908864 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1550881 ]

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

                Created:
                Updated:
                Resolved: