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

Incorrect contexts for Epic related fields

XMLWordPrintable

      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

        1. epic1.png
          epic1.png
          47 kB

          Form Name

            [JSWSERVER-9552] Incorrect contexts for Epic related fields

            Bugfix Automation Bot made changes -
            Minimum Version New: 6.02
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2853052 ] New: JAC Bug Workflow v3 [ 2934092 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545028 ] New: JAC Bug Workflow v2 [ 2853052 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1551811 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545028 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: affects-server fixme ondemand st10 New: affects-cloud affects-server fixme ondemand st10
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: fixme ondemand st10 New: affects-server fixme ondemand st10
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 909779 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1551811 ]

            Richard Stimson added a comment -

            I had this issue and found that it was due to 'Epic Name' field not being on the screen for certain projects.
            Admin menu->Issues->Screens. Make sure 'Epic Name' is on all the screens that you use.

            Create Epic now works for me. Hope this helps.

            Richard Stimson added a comment - I had this issue and found that it was due to 'Epic Name' field not being on the screen for certain projects. Admin menu->Issues->Screens. Make sure 'Epic Name' is on all the screens that you use. Create Epic now works for me. Hope this helps.

            Oswaldo Hernandez (Inactive) added a comment -

            Hi jeff809062307,

            As per my comment above we believe that the issue reported here has been obsolete since JIRA 6.1.6 and the upgrade tasks that were run for upgrades from JIRA Agile 6.2.2.

            Consequently, could you please raise a support request with us at https://support.atlassian.com so that we can review what is happening to you instance and troubleshoot with you further?

            Thanks in advance.

            Regards,

            Oswaldo Hernández.
            JIRA Bugmaster.
            [Atlassian].

            Oswaldo Hernandez (Inactive) added a comment - Hi jeff809062307 , As per my comment above we believe that the issue reported here has been obsolete since JIRA 6.1.6 and the upgrade tasks that were run for upgrades from JIRA Agile 6.2.2. Consequently, could you please raise a support request with us at https://support.atlassian.com so that we can review what is happening to you instance and troubleshoot with you further? Thanks in advance. Regards, Oswaldo Hernández. JIRA Bugmaster. [Atlassian] .

            Jeff Galbraith added a comment -

            We are new users to Jira and installed v7.1.7#71011 and this is exactly happening to us as detailed above.

            Jeff Galbraith added a comment - We are new users to Jira and installed v7.1.7#71011 and this is exactly happening to us as detailed above.

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

                Created:
                Updated:
                Resolved: