Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-59074

Required fields does not show up when creating a new epic from plan view

XMLWordPrintable

    • 7
    • 8
    • Severity 3 - Minor
    • 14
    • Hide
      Atlassian Update – 14 December 2018

      Hi everyone,

      We have recently reviewed this issue and the overall interest in the problem. Since the issue hasn't collected votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future, i.e. in the next 6 months.

      Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

      Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

      Katarzyna Derenda
      Product manager, Jira Server

      Show
      Atlassian Update – 14 December 2018 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. Since the issue hasn't collected votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future, i.e. in the next 6 months. Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Katarzyna Derenda Product manager, Jira Server

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      Steps to reproduce

      1. Modify field configuration and make Affects Version a required field
      2. Create new Scrum Sample board
      3. Click on + to create a new epic

      Excepted Result

      Required fields show up

      Actual Result

      Affects Version is missing

      This does not only apply to the Affects Version field, but any required field.

      Workaround

      • Add field to appropriate screen (See Defining a Screen)
      • Create Epic by clicking on Create button on top bar.

        1. AffectedVer.png
          150 kB
        2. MissingField.png
          145 kB

            [JRASERVER-59074] Required fields does not show up when creating a new epic from plan view

            Alexander Christian added a comment -

            Still exists, even in current Jira Cloud version.

            Alexander Christian added a comment - Still exists, even in current Jira Cloud version.

            Peter Heubeck added a comment -

            The problem still exists in 7.12.3.

            How hard can it be to just launch the Create screen defined for Epics in selected project as the ordinary Create button does?

            BR, Peter

            Peter Heubeck added a comment - The problem still exists in 7.12.3. How hard can it be to just launch the Create screen defined for Epics in selected project as the ordinary Create button does? BR, Peter

            Aravind Viswanathan added a comment -

            Hi Team,

            We are noticing this issue in JIRA version 7.2.7

            Could you please let us when the same will be fixed and deployed.

            Thanks

            Aravind Viswanathan.

             

            Aravind Viswanathan added a comment - Hi Team, We are noticing this issue in JIRA version 7.2.7 Could you please let us when the same will be fixed and deployed. Thanks Aravind Viswanathan.  

            JMcDonnell added a comment - - edited

            Still not resolved. Raised initially in 2013! In effect, the team can work exclusively from the board.

            JMcDonnell added a comment - - edited Still not resolved. Raised initially in 2013! In effect, the team can work exclusively from the board.

            antonio_jesus_nunez added a comment -

            I have the same bug with JIRA 7.1.1

            antonio_jesus_nunez added a comment - I have the same bug with JIRA 7.1.1

            Brendan Byers added a comment -

            Hello Paulwyn,

            Is there any update on this issue?
            We're still not seeing this fix on our server.

            Thank you,
            Brendan Byers

            Brendan Byers added a comment - Hello Paulwyn, Is there any update on this issue? We're still not seeing this fix on our server. Thank you, Brendan Byers

            Paulwyn Devasundaram (Inactive) added a comment -

            Hi bbyers
            I'm Paulwyn, a developer in the JIRA team. We are investigating why the fix for this isn't working.
            We'll let you know as soon as we have an update.

            Thanks!

            Paulwyn Devasundaram (Inactive) added a comment - Hi bbyers I'm Paulwyn, a developer in the JIRA team. We are investigating why the fix for this isn't working. We'll let you know as soon as we have an update. Thanks!

            Brendan Byers added a comment -

            Is there additional configuration that is required to get this to work?

            I have set required custom fields on a 7.0.9 instance server and am still encountering the issue of them not appearing.

            Brendan Byers added a comment - Is there additional configuration that is required to get this to work? I have set required custom fields on a 7.0.9 instance server and am still encountering the issue of them not appearing.

            Gareth Williams added a comment -

            7.1.0-OD-04 shipped to Cloud.

            Gareth Williams added a comment - 7.1.0-OD-04 shipped to Cloud.

            Kelly Schoenhofen added a comment -

            Jira 7.0 went generally available to the public on Oct 6th, 2015. Four weeks after GA, we still had three critical plugins not 7.0.0 compatible; I emailed the vendors, all three responded and they had 7.0 compatible versions available within 10 days. A week of sandbox testing and we upgraded to 7.0 in Production, sans a couple non-critical add-ons (like Clone And Move).

            It's been 3 full months since Jira 7.0 went GA, if you have critical add-ons still not compatible with Jira 7, I would first use email to contact them, and second, use your feet. Walk away and don't re-up with companies that can't keep up with their partner (you!). You deserve better.

            With the birth of the 20lb 7.0 baby, I expect Atlassian to pick up the pace again (Jira 6.4 came out in March) and start delivering innovation & improvements at the pace I grew accustomed to (and voted with my limited tools budget). If other companies want to play in this field, they need to keep up or get out.

            -Kelly

            Kelly Schoenhofen added a comment - Jira 7.0 went generally available to the public on Oct 6th, 2015. Four weeks after GA, we still had three critical plugins not 7.0.0 compatible; I emailed the vendors, all three responded and they had 7.0 compatible versions available within 10 days. A week of sandbox testing and we upgraded to 7.0 in Production, sans a couple non-critical add-ons (like Clone And Move). It's been 3 full months since Jira 7.0 went GA, if you have critical add-ons still not compatible with Jira 7, I would first use email to contact them, and second, use your feet. Walk away and don't re-up with companies that can't keep up with their partner (you!). You deserve better. With the birth of the 20lb 7.0 baby, I expect Atlassian to pick up the pace again (Jira 6.4 came out in March ) and start delivering innovation & improvements at the pace I grew accustomed to (and voted with my limited tools budget). If other companies want to play in this field, they need to keep up or get out. -Kelly

              Unassigned Unassigned
              cshim ChrisA
              Affected customers:
              79 This affects my team
              Watchers:
              61 Start watching this issue

                Created:
                Updated: