IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

      Issue Summary

      Currently, when the user changes the epic status first, the status is visible in the board view, but after a few seconds, the epic status disappears.

      Steps to Reproduce

      1. Create an Epic issue under Jira Software project (scrum)
      2. In the board view, Select a group by Epic
      3. Open the Epic issue that you just created and change the Epic status
      4. You will notice that for a few seconds, epic status is visible under the board view, but after a few seconds, Epic status disappears.

      Expected Results

      Epic Status should appear in the board view.

      Actual Results

      Epic Status is not appearing in the board view.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

                Issue Summary

                Currently, when the user changes the epic status first, the status is visible in the board view, but after a few seconds, the epic status disappears.

                Steps to Reproduce

                1. Create an Epic issue under Jira Software project (scrum)
                2. In the board view, Select a group by Epic
                3. Open the Epic issue that you just created and change the Epic status
                4. You will notice that for a few seconds, epic status is visible under the board view, but after a few seconds, Epic status disappears.

                Expected Results

                Epic Status should appear in the board view.

                Actual Results

                Epic Status is not appearing in the board view.

                Workaround

                Currently, there is no known workaround for this behavior. A workaround will be added here when available

                        vle2@atlassian.com Vu Le
                        f91199aa80c0 Dilip
                        Votes:
                        1 Vote for this issue
                        Watchers:
                        7 Start watching this issue

                          Created:
                          Updated:

                            vle2@atlassian.com Vu Le
                            f91199aa80c0 Dilip
                            Affected customers:
                            1 This affects my team
                            Watchers:
                            7 Start watching this issue

                              Created:
                              Updated: