Bulk Documentation
Product referenceImprovement and complianceQuality

Create a quality issue

Create a quality issue on one scrolling form. Set source, title, colored severity, category, quantity, and evidence, and filter the job from a column header.

Last updated

A quality issue is the record you keep when a defect, non-conformance, or quality observation needs to be tracked instead of fixed without a trail. Creating one captures what went wrong, how many units are affected, and how severe it is, then gives the problem a number you can review and close later.

This guide covers the Create Quality Issue page, the form you use to log an issue by hand. It is one scrolling page. Every section is on the page at once. There is no step indicator and no preview panel.

Permission required

You need the Create quality issues permission (quality_issues.create) to save the issue. The built-in Quality, Entity admin, and Super user roles include it. The default Operator and Manager roles do not. A custom role can include or omit it. The New Issue button is still shown if you lack the permission. If Create issue is refused, ask an administrator to grant Create quality issues.

Before you begin

  • Confirm your role includes Create quality issues.
  • Know the job or work order, the affected part, and about how many units are impacted, if you have that context. Linking a job is optional.
  • Categories are optional. If you want to classify the defect, an administrator can set them up first. Each category has a severity, and choosing one on this form applies that severity. See Configure quality categories and root causes.

Open the form

You can open the form from more than one place:

  • On Quality home, select New, then New Issue.
  • On the Quality Issues list, select New Issue in the header. When the list is empty and no filters are active, the empty state offers Log Issue instead. If filters hide every row, that empty state has no Log Issue button. Use the header New Issue button.
  • Go directly to /quality/issues/new.

The page title is Create Quality Issue. The subtitle is Capture a new quality issue and optionally link it to production context. The sections, from top to bottom, are Source, Details, Severity, Impact, Affected Items, and Evidence.

Source

Source asks where the issue originated. Production Job is selected when the form opens. The choices are:

  • Production Job. Issue linked to a specific work order or batch.
  • Inspection Failure. Generated from a failed QC checklist item.
  • Standalone Issue. General observation not linked to a specific job.

Choosing Inspection Failure records that source. This form does not ask you to pick a checklist item.

Details

Details asks you to describe the problem.

  • Issue Title is required. The label shows an asterisk. Use a short summary, up to 200 characters. The placeholder is Brief summary of the defect.
  • Problem Description is optional. It has no asterisk. You can enter up to 500 characters. A counter under the field shows how many you have used, for example 12/500 characters. The placeholder is Provide detailed observation...

Pressing Enter in Issue Title does not create the issue.

Severity

Severity asks how critical the issue is to production. The choices use the same colors as CAPA priority:

  • Low (gray). Minor impact. Production can continue with normal oversight.
  • Medium (amber). Noticeable defect. Plan a response in the current shift.
  • High (orange). Serious impact. Address before it spreads downstream.
  • Critical (red). Production stop or safety risk. Act immediately.

The form opens on High. Select a card to change it. You can change it again after you pick a category.

Impact

Impact asks you to categorize the defect and provide initial findings.

  • Issue Category is optional. The placeholder is Select category.... Search with Search categories.... If the site has no categories, the list says No categories found. Choosing a category sets severity to that category's severity. You can still pick another severity card. Clearing the category leaves the severity you already chose.
  • Affected Quantity starts at 1. The label has no asterisk, but the form will not create the issue unless the number is greater than zero. The unit selector beside it is optional. Its placeholder is Unit. Search with Search units.... If none match, it says No units found. Production units are listed first, and their description includes (Production).
  • Preliminary Root Cause (Optional) is a note for any initial findings. The placeholder is Any initial findings....

Affected Items

Affected Items asks you to identify the affected job. You can leave this empty and still create the issue, including when Production Job is selected.

The table links one job. Select a row to choose it. Select a different row to replace that choice. A header checkbox is shown, but it does not select every job on this form.

The search box placeholder is Search by Job Number, Order # or Product...

The table starts with Job Number and Due Date. Select Columns to show more: Current Resource, Next Resource, Routing, Customer, Product, PO Number, Order #, Priority, Qty, and job custom fields when the site has them.

Filters come from the column header, not from a separate filter panel. Select a header, or right-click it. The menu is titled with that column and includes Filter, Search values, Select all, and Clear. Tick the values you want, including (Blanks) when that row is offered. Due Date lists calendar dates by year, then month, then day. A filtered header shows a funnel marked Filtered. If the value list is long, it says Showing the first 1,000 values. Search to find more.

When a job is selected, Clear appears beside Columns and removes that job. Selecting a job also stores that job's product on the issue. Clearing the job clears that product link.

If nothing matches, the table says No jobs found matching your filters. If the site has no jobs to show, it says No jobs available. Use Previous page and Next page to move through the list. The table shows five jobs per page.

Evidence

Evidence asks you to upload photos or documents related to the issue. This is optional.

The drop zone says Click to upload or drag and drop, and SVG, PNG, JPG or PDF (max. 10MB). You can add up to 10 files. The file picker also accepts Word (.doc, .docx) and Excel (.xls, .xlsx) files. While a file is uploading, the zone says Uploading.... After a file is added, the form shows its name and size, and a count such as 1 of 10 files uploaded. Select the close control on a file card to remove it.

If a file is over the limit, the form reports that it exceeds 10MB. If you pick more files than the remaining slots, it says how many more can be uploaded, in the form Only N more file(s) can be uploaded.

This form does not ask you to assign an inspector or a team.

Create the issue

The bottom of the form is a status line plus Cancel and Create issue. It is not another titled section.

Until the title is filled in and the affected quantity is greater than zero, the status line reads Complete the required fields first. Create issue still responds to a click. That click does not save. It moves focus to the title, or to the quantity if the title is already filled and the quantity is not greater than zero. When the form can be saved, the status line reads Ready to create.

Select Create issue to save. The status line changes to Creating the issue... while Bulk saves, and the button shows a spinner. The button label stays Create issue. Pressing Enter in a field does not submit the form.

Cancel, and the back arrow (Go back), leave the form. If you changed the source, the title, the description, or the category, Bulk asks Discard changes? The message is You have unsaved changes. Are you sure you want to cancel? Your progress will be lost. Select Continue Editing to stay, or Discard Changes to return to the Quality Issues list. Severity, quantity, the unit, the root-cause note, the linked job, and uploaded files do not raise that question on their own. If none of the tracked fields changed, Cancel returns to the list without asking.

What happens after you submit

When the issue is created, Bulk:

  • Assigns a number in the form QI-YYYY-NNNN, such as QI-2026-0001. The sequence is padded to four digits and restarts each calendar year for the site.
  • Saves the issue with status Open and disposition Pending.
  • Shows a confirmation such as Issue QI-2026-0001 created.
  • Opens the new issue. Back from that page does not return to this form. It returns to the previous page, usually the Quality Issues list.

From the issue you can review evidence, set a root cause, and later disposition and close it. See Review and close a quality issue.

This form does not create a non-conformance report. To raise one, use Create an NCR.

Granite Peak Manufacturing example

At the Leeds Fabrication Plant, an inspector finds weld porosity on 12 steel mounting brackets during a first-off check. They open Quality Issues, select New Issue, and fill the scrolling form:

  • Leave Source on Production Job.
  • Set Issue Title to Weld porosity on mounting bracket batch.
  • Describe the pin-holes along the fillet welds in Problem Description.
  • Leave Severity on High, or set it again if a category changes it.
  • Pick the site's weld category under Issue Category, if one exists.
  • Set Affected Quantity to 12 and choose a unit.
  • In Affected Items, search or filter from the Job Number header and select the bracket job.
  • Under Evidence, upload two close-up photos.
  • Select Create issue.

Bulk confirms the new number, opens the issue as Open with disposition Pending, and leaves a tracked record to investigate.

Feature state and limitations

This capability is generally available.

  • NCR escalation is a separate flow. This page creates a quality issue only. It does not send an escalate-to-NCR choice, and it shows no NCR or hold toggle.
  • Problem Description is optional. It has no required asterisk. Only the title and an affected quantity greater than zero are required to create the issue. A source is always selected, and it starts as Production Job.
  • A job is optional. Choosing Production Job does not force you to select a row.
  • There is no assignee on this form. You do not pick an inspector or a team while creating the issue.
  • Cancel only tracks some edits. The discard question appears after a change to the source, title, description, or category. Other edits do not trigger it by themselves.
  • Enter does not create the issue. Select Create issue.

Troubleshooting

  • Create issue does not save. Read the status line. Complete the required fields first. means the title is empty or Affected Quantity is not greater than zero. Select Create issue to move focus to the missing field.
  • Create issue is refused. Your role is missing Create quality issues (quality_issues.create). Ask an administrator to grant the Quality, Entity admin, or Super user role, or a custom role that includes that permission.
  • You cannot find New Issue. On Quality home, open New and choose New Issue. On the Issues list, use the header New Issue button. Log Issue appears only in the empty state when no filters are active.
  • Issue Category says No categories found. No quality categories are configured for this site. See Configure quality categories and root causes.
  • The job table is empty. No jobs available. means there is nothing to list. No jobs found matching your filters. means the search box or a column filter is hiding rows. Clear the search, or open the filtered header and select Clear.
  • A new job is missing. If the table says New records are still syncing. Latest results may not appear yet., wait and search again.
  • A file will not upload. The drop zone allows up to 10 files, and each file must be 10MB or smaller. The message names the file that exceeds the 10MB limit.