1113113 - Impossible to create a new bug when there is only 1 product in Component in the list and a mandatory custom field which is only displayed when this Component is selected

Status: NEW

(Bugzilla :: Creating/Changing Bugs, defect)

Description

[Christophe JAILLET]

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:34.0) Gecko/20100101 Firefox/34.0
Build ID: 20141125180439

Steps to reproduce:

Create only 1 component for a given product.
Define a new Mandatory custom field that is only displayed when this Product/Component is selected.

When you create a new bug, the only 1 component in the list is pre-selected when the page is displayed, but the Mandatory Custom field is not.

So it is not possible to create a new bug and a error message is displayed when to try to submit the bug



Expected results:

The Custom field should be displayed when the page is displayed, when there is only one Component is this one is automatically selected.

A work-around is to create a 2nd dummy Component. In this case the Component is *not* already selected in the list when the page is loaded and the custom field is correctly displayed when the Component is selected.

Comment 1

[Christophe JAILLET]

Another way to trigger the behavior:
if you meet some criteria to display a custom field, it is displayed. OK.

Then if you change the language used for the display, then the page is reloaded with all the already selected values *but* the custom field linked to these values does not display anymore.
For it to be displayed again, you have to select something else, then reselect what is the condition of appearance of the custom field.

Comment 2

[Christophe JAILLET]

Was with bugzilla 4.4.6

Comment 3

[Frédéric Buclin]

If you only have one single component, it's much better to define the custom field as being displayed when product X is selected than its component Y. The workaround is easy.

Comment 4

[Christophe JAILLET]

Obviously correct.

I did it that way because I plan to extend it later on.

However, I can also adjust my display rule later, when I will add more Components, as well. So I have changed my configuration based on your remark.
Switching from one language to another is just a very minor issue which should never happen in real life.

Comment 5

[Christophe JAILLET]

Another case of the 'non display of custom fields' is when you save your change, if an error occurs (in my case it was attachment size too big), then you have to click on back in the browser.

Then (at least with FF 35), all the fields are initialized BUT the custom field is not displayed either. I still have to unselect/reselect what it is linked to in order to display it.

Comment 6

[Christophe JAILLET]

Another case: if you try to move a bug from one product to another one.

First, you change the product.
Then you are prompted to select the version and a component.
If the component you choose has some mandatory field, then you can not proceed further.


A workaround is to first change to a component of the same product which don't have any mandatory field and then, change the component to the right one. In this case, the mandatory fields will be displayed and you will be able to choose what you want.

Comment 7

[Christophe JAILLET]

Related to bug 1183398?

Comment 8

[JK]

Another case:

• Show list of all bugs for the selected component.
• Use link at the bottom of the page ("File a new bug in the "XXX" component of the "YYY" product). The URL in such case is: "enter_bug.cgi?product=YYY&component=XXX"

Component field is preselected, but the fields related to this component are not shown.