In some instances, Epic-specific fields (Epic Status, Epic Name etc.) appear as assigned to other Issue Types, and so show up as Required in screens that are not relevant. This affects different Issue Types.
      Example:

      Workaround:

      Restart Jira Instance (in most cases corrections scripts will run at the start and fix the problem)

      If restart doesn't work try the workaround: Epic Name field is required on Create Issue Screen for other Issue Types

            [JSWSERVER-9552] Incorrect contexts for Epic related fields

            No work has yet been logged on this issue.

              Unassigned Unassigned
              dwierzbicka Dobroslawa Wierzbicka (Inactive)
              Affected customers:
              9 This affects my team
              Watchers:
              24 Start watching this issue

                Created:
                Updated:
                Resolved: