Bug 1116744 - Indicate that sub components are required when creating a bug
Summary: Indicate that sub components are required when creating a bug
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Bugzilla
Classification: Community
Component: Creating/Changing Bugs
Version: 4.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: 4.4
Assignee: Matt Tyson 🤬
QA Contact: Simon Green
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-07 08:32 UTC by Moritoshi Oshiro
Modified: 2018-12-09 06:29 UTC (History)
4 users (show)

Fixed In Version: 4.4.4022
Clone Of:
Environment:
Last Closed: 2014-07-28 00:42:59 UTC
Embargoed:


Attachments (Terms of Use)

Description Moritoshi Oshiro 2014-07-07 08:32:14 UTC
Created attachment 915998 [details]
screenshot

Description of problem:
When creating a bz ticket for kernel component, a user tries to complete a new one without specifying Sub Component and it results an error. 

The sub component of kernel is not stated as "* = Required Field" in the new creation page, but it looks like a required field. 

Please put the * next to sub component showing a user that it is a required field or fix the submission such that sub component is not specified but it can be submitted.  


Version-Release number of selected component (if applicable):


How reproducible:
Always 

Steps to Reproduce:
1. Select kernel as a component
2. Do not select sub component of kernel
3. Fill in other fields
4. Submit the new report

Actual results:
Error occurs and submitting a new report fails.

Expected results:
Error does not occur and submitting a new report succeeds.
OR
Specify "* Sub Component" indicating that it is a required field. 




Additional info:
Please see uploaded file which is a screen shot of partial page.

Comment 2 Matt Tyson 🤬 2014-07-13 23:22:11 UTC
Sub components will now show an asterisk where applicable.

Comment 3 Matt Tyson 🤬 2014-07-28 00:42:59 UTC
This change is now live. If there are any issues, do not reopen this bug.
Instead, you should create a new bug and reference this bug.


Note You need to log in before you can comment on or make changes to this bug.