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

Create Epic dialog does not remember which fields should be displayed

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

      Description
      The Create Epic dialog allows to configure which fields are to be displayed. Unfortunately, these settings are forgotten the next time you want to create an epic.

      Steps to reproduce

      Note: Our JIRA is configured to require a component for each issue

      • click on "create epic" button/link in the planning board
      • Fill in Epic name and summary
      • select "create"
      • you get error message: "Component/s should be modified during this transition."
      • select "configure fields", activate "Component/s"
      • select "Component"
      • click "create"
      • click on "create epic" again

      result
      The Component/s field is not displayed

      expected result
      The Component/s field should be always displayed unless I remove it again

            [JSWSERVER-9339] Create Epic dialog does not remember which fields should be displayed

            Paul Jarman added a comment -

            Bug is in 10.3.7

            Paul Jarman added a comment - Bug is in 10.3.7

            Hi,

             

            This problem exists in 9.12.5 data center version too.

            Danske Bank Atlassian Support added a comment - Hi,   This problem exists in 9.12.5 data center version too.

            Any update about that?

            Matheus Motta dos Santos added a comment - Any update about that?

            Ping

            Kaz Gerritsen added a comment - Ping

            Ping

            Joel Hägglund added a comment - Ping

            any update 

            Rajesh Devadasan added a comment - any update 

            Marion Denny added a comment - - edited

            Jira team - can you please address this?  This has been open for EIGHT YEARS. This defect is super annoying and impacts my workflow.  

            Marion Denny added a comment - - edited Jira team - can you please address this?  This has been open for EIGHT YEARS. This defect is super annoying and impacts my workflow.  

            Hi,
            we have the issue too. We use the components to structure our work better. Our filters are used in the boards which filter based on these components.

            Unfortunately the user does not get the field automatically.
            Please develop a solution. 

            Rene Happich added a comment - Hi, we have the issue too. We use the components to structure our work better. Our filters are used in the boards which filter based on these components. Unfortunately the user does not get the field automatically. Please develop a solution. 

            Azfar Masut added a comment - - edited

            Its an annoying bug. Why? Because we used scriptrunner to make some field as required. So when people create the epic through that panel, the required field doesnt get shown, and no warning whatsoever is thrown about that required field. As its hidden, user doesnt know what's wrong and they wont be able to create the epic. Resulted for them to have to use the top red 'create button' instead - which as I mentioned, an annoyance to the user, and defeat the purpose of having that quick epic create issue link in the first place

            Azfar Masut added a comment - - edited Its an annoying bug. Why? Because we used scriptrunner to make some field as required. So when people create the epic through that panel, the required field doesnt get shown, and no warning whatsoever is thrown about that required field. As its hidden, user doesnt know what's wrong and they wont be able to create the epic. Resulted for them to have to use the top red 'create button' instead - which as I mentioned, an annoyance to the user, and defeat the purpose of having that quick epic create issue link in the first place

            BernardH added a comment -

            I find it amazing that simple problems exist like this and have not been fixed 5 years after being reported. It is the same logic as being used on the Blue Create Icon,. Why it does not work everywhere you can customize the fields is beyond me.  Another simple one. Creating a Version via the Create Version button vs going to Releases and creating a version. Why is there a character limitation in one that is half the character limitation of the other. Again, a simple fix that eludes the attention of the developers. Who is the PO anyway?

            BernardH added a comment - I find it amazing that simple problems exist like this and have not been fixed 5 years after being reported. It is the same logic as being used on the Blue Create Icon,. Why it does not work everywhere you can customize the fields is beyond me.  Another simple one. Creating a Version via the Create Version button vs going to Releases and creating a version. Why is there a character limitation in one that is half the character limitation of the other. Again, a simple fix that eludes the attention of the developers. Who is the PO anyway?

              Unassigned Unassigned
              6d38728fe0e9 Jens Göring
              Affected customers:
              45 This affects my team
              Watchers:
              46 Start watching this issue

                Created:
                Updated: