Flag, track, and resolve issues, including process and part non-conformances throughout the application.

With multiple ways to create and manage issues, we recommend reading through this entire guide to gain a full understanding of this feature.

Click on the Issues module on the left navigation pane to navigate to the Issues landing page.

See all open and closed Issues at a glance, including severity and status.

Filter the page by Tags or References.

Filter by References allows you to filter the list by the specific Part, Item, Run, Purchase Order, Step, Work Order, Tool, or Risk associated.

Click Add and select an Entity Type from the drop down. Select the Entity from the Name drop down. Add as many Entities as desired to the filter.

Further details may be required depending on the Entity Type.

Once all desired Entities have been selected, click save to apply the filter.

To create a new issue for a run, or to add the run to an existing issue, click on this icon at the top of the page and then select the corresponding option.

Select the existing Issue from the drop down menu, or fill in the details in the modal to create a new Issue.

Enter a Name for the issue. (required)

Select a Project from the dropdown menu. If the Procedure is already assigned to a Project, that field will be pre-filled and locked.

Select the Severity from the drop down list:

Select Assignee and/or Collaborators from the drop down list of users in your workspace.

Add any Notes or Attachments, and then click Create Issue.

The new Issue will be created in the Draft state and will be visible in the Issues drop down on the run.

Click into an issue to view or edit details, including changing the status and viewing activity. In the Reference section, there will be links to anything associated with the issue.

Navigate to the Issues module to see a list of all Open or Closed issues. Use the search bar, filter or sort columns to quickly find the Issue you're looking for. Click into an issue to bring up the view or edit options as seen above.

To flag issues related to specific steps, click the 3 dot menu in the top right corner of any step to Add Issue.

The process to create, review, and edit a step issue is the same as a run issue.

The Reference link from the Issues module and Issue details page will link directly to the step associated with that issue.

When an issue is marked as Critical, the run will automatically be paused until the issue has been downgraded or marked as resolved.

Hover over the issues icon to see details on when the run was paused.

Once all critical issues for the run have been resolved or downgraded to Major or Minor, the run can be resumed.

The Issues icon in the top toolbar now provides clearer visibility into open issues across the application.

In addition, items with Critical issues now show a more prominent visual indicator, including a red bar across the top of the item view, making Critical status easier to spot.

To create an issue associated with a Part Revision, navigate to the Part Details screen for the desired part revision and the Issues Icon. You can create a new Issue or add to an existing Issue.

Click Create Issue and fill out the Issue information as seen below.

Click Create Issue.

Issues will be displayed on the Parts Detail screen and on the main Issues screen.

Click on the Issue number to be directed to the specific Issue to view or edit.

To create an Isssue for a PO, navigate to a PO in a Draft or Submitted state (Issues is not currently supported for Closed or Cancelled POs) and click the Issues Icon. You can create a new Issue or add to an existing Issue.

Click Create Issue and fill out the Issue information in the pop-up window.

Click Create Issue.

Issues will be displayed on the PO Detail screen and on the main Issues screen.

Click on the Issue number to be directed to the specific Issue to view or edit.

To create an Issue associated with an Inventory Item, navigate to the Inventory screen, click into the specific item, and click on the Issues Icon.

Click Create Issue and fill out the Issue information in the pop-up window.

Click Create Issue.

Issues will be displayed on the Item Detail screen and on the main Issues screen.

Click on the Issue number to be directed to the specific Issue to view or edit.

Clicking into an Issue from the Issues list will bring you to the Issue Details page.

In addition to being able to view/edit Project, Status, Severity, Assignees, Collaborators, and Tags — the issue details page also provides an Activity log. Any activity or changes related to creating, pausing, resuming, or editing issues will be tracked here.

The References section will display links to anything that has been associated to this Issue.

The Activity Log allows for adding comments, including images.

You can insert Snippets directly into an Issue Action step. Add a content Snippet, or insert a compatible step Snippet (for example, one whose roles are compatible with an Issue Action step).

When building a Snippet in the Snippets library, if you add content that isn't compatible with Issue Actions (for example, a field input), a banner will indicate that the Snippet can only be used in procedures and will list which content blocks are compatible with Issue Actions.

Click on the 3 dot menu and select Edit Issue to add notes, files/attachments, and Issue Actions (e.g. steps required to resolve the issue)

Change/edit any part of an Issue while it's in Draft mode.

Similar to Steps in a Procedure, Issue Actions include Step names, Signoffs, and Content Blocks.

Once Issue Actions are completed, click Close and select Resolved or Won't Fix. Click Confirm to close the issue.

Use Issue Types to standardize how different categories of issues are created, assigned, and resolved. Each type can use its own Issue Form, default values, icon, and seeded action steps, allowing teams to capture the right information and follow the correct workflow from the moment an issue is created.

Issue Forms allow you to create pre-defined templates for issues within your workspace. To access the Issues form, head to the Issues Settings (gear icon) and then Issue Form:

Multiple Forms can be created and will each have their own layout, custom fields, and default values.

Select the + Create Form button to create a new Form.

Use the pencil icon to edit the Form title.

Click Edit to make changes to the form layout, including adding new Custom Fields.

From here, you will be able to edit and drag/drop the sections to rearrange existing fields in the issue form:

You can also add new fields, rich text and images to enhance your form:

These options will add new content blocks to your issue form, which you can then reposition anywhere you’d like in the Issue Form:

This new content will be automatically incorporated into every new issue that is created using that form:

You can configure a default value for custom fields directly on an individual Issue Form. When a default value is set, that value will automatically populate the custom field when creating similar Issue entries, reducing repetitive data entry.

To set a default value, navigate to Issues Settings > Issue Form.

On the Issue Form, click Edit Fields.

Hover over any field and click the pencil icon.

In the modal, there is an option to set a default value specific to the type of entry for the field. ex: Number, Text Block, List options etc:

The default value is optional but when configured will display that value automatically. The default value can be edited, but this allows for faster repetitive data entry.

When inputting start and end dates to your issues, you will be able to auto-calculate the resolution time:

Within your new issue, you wil also be able to see all activity for that issue The activity log can also be collapsed:

Open the Issues module, select the settings gear, and then select Issue Types from the Issues Settings navigation.

The Issue Types page separates active configurations into Open and Archived tabs.

The list shows each type's name and description. A star identifies the current team default, and any configured icon is displayed alongside the type name.

From the Issue Types page, click + New Type. The New Issue Type window defines the identifying information, default behavior, form, and initial action plan for every issue created with that type.

Enter a unique Issue Code and a descriptive Name. The code provides a concise identifier for the type and will be used as a prefix in Issue numbering, while the name is what users select when creating an issue.

Add a description that clearly explains when the type should be used.

Select an Icon to make the type easier to recognize in lists and menus. The selected icon is shown next to the type after it is created.

Use the Form field to choose the Issue Form that should be displayed when this type is selected. You can select an existing form or choose + New blank form to create a new form for the type.

The form determines the standard and custom fields available on the issue. This allows different issue categories—such as non-conformance reports, safety concerns, supplier issues, or internal corrective actions—to collect different information while remaining within the same Issues workflow.

Set any values that should automatically populate when a user creates an issue of this type:

Default Severity sets the initial severity.

Default Status sets the issue's initial workflow status.

Default Assignee automatically assigns the issue to the selected user.

These defaults reduce repetitive data entry and help ensure consistent triage. Users can update editable values during issue creation when a different value is needed.

Use Default Action Steps to build the starting resolution workflow for the type. These steps are copied into every new issue created with this configuration.

Enter a step name, configure the required signoff, and use Add Content to include the content needed to complete the step. Available content includes informational and input blocks such as warnings, requirements, file attachments, links to procedures, field inputs, field input tables, and tables.

Use the step controls to expand or collapse the step and open its additional settings. Default action steps are intended for work that should be present on every issue of the type; issue-specific steps can still be added later while managing an individual issue.

Select Set as team default when this should be the type initially selected for new issues. The default can also be changed later from the Issue Types list.

Click Create to save the Issue Type.

Open the three-dot menu at the end of an Issue Type row to manage the configuration. The available actions are:

Edit — Update the type's code, name, description, icon, form assignment, defaults, or seeded action steps.

Edit Form — Open the Issue Form assigned to the type and change its layout or field configuration.

Set as Default — Make the selected type the team default for newly created issues.

Archive — Remove the type from active use while retaining the configuration in the Archived tab.

Archived types: Archived configurations are separated from open Issue Types. This helps preserve historical configuration without presenting an obsolete type as an option for new issues.

When creating a new issue, use the Type dropdown to select the appropriate Issue Type. The selected type controls the form displayed in the Create New Issue window.

After the type is selected, Epsilon3 loads the assigned form and applies defaults configured in both places:

Issue Type defaults, including severity, status, assignee, and seeded action steps.

Issue Form defaults, including configured default values for custom fields.

Complete the remaining fields, including the issue name, project, collaborators, notes, attachments, and any custom fields provided by the selected form. Then click Create Issue.

Form behavior: Changing the selected Issue Type changes the form and defaults used for the new issue. Select the correct type before completing type-specific custom fields.

Within the Issue Settings > General, you can also enable strict issue permissions to restrict certain users from being able to edit issues while still allowing all paid users to comment:

The Parts grid in the Builds module includes additional demand-planning insights to help teams understand inventory usage patterns, anticipate shortages, and plan reorders more effectively. These enhancements surface key metrics directly in the Parts list so teams can act quickly without exporting data or manually calculating demand.

Several new columns are available in the Parts grid to provide visibility into current and future inventory needs.

Current Demand shows how many units of a part are currently required across open work, helping teams understand near-term demand.

On Order reflects quantities already included on open purchase orders, giving visibility into incoming supply.

Avg Monthly Demand calculates the average rate at which a part is consumed over time, providing a baseline for forecasting.

Demand Shortfall highlights the gap between available inventory plus incoming supply and expected demand.

Days to Stockout estimates how long current inventory will last based on historical usage trends.

Est. Reorder Date suggests when a reorder may be needed to avoid running out of stock.

Together, these columns allow teams to evaluate supply health at a glance and prioritize procurement actions before shortages occur.

To make it easier to identify parts that require attention, the Parts grid now includes warning-based filters. These filters allow users to quickly surface parts that are at risk of running out or falling below defined thresholds.

Avg Monthly Demand calculates the average rate at which a part is consumed over time, providing a baseline for forecasting.

Demand Shortfall highlights the gap between available inventory plus incoming supply and expected demand.

Days to Stockout estimates how long current inventory will last based on historical usage trends.

Est. Reorder Date suggests when a reorder may be needed to avoid running out of stock.

Together, these columns allow teams to evaluate supply health at a glance and prioritize procurement actions before shortages occur.

To make it easier to identify parts that require attention, the Parts grid now includes warning-based filters. These filters allow users to quickly surface parts that are at risk of running out or falling below defined thresholds.

Available warning filters include:

Applying these filters helps teams focus on the most critical items first and take corrective action sooner.

By combining real-time demand metrics with warning-based filtering, teams can move from reactive inventory management to proactive planning. These insights help prevent production delays, reduce last-minute procurement, and ensure inventory levels stay aligned with actual usage.

Issue Insights provides a high-level analytics view of your workspace’s issues so you can quickly understand patterns, not just individual records. From the Issues module, select Insights in the left navigation to open the dashboard.

This page helps answer key questions like where issues are concentrated, whether they are increasing over time, how severe they are, and which parts or items are most commonly involved.

This view is separate from the Issues list and is focused on reporting and trend analysis rather than managing individual issues.

Use the available filters to refine your view:

All charts update dynamically based on your selections, making it easy to investigate spikes, trends, or specific areas of concern.

Issue Insights includes four key charts:

Issues by Project can only be filtered by one project or all projects, however clicking on the name of the project to the right of the pie chart will exclude that project.

This will be denoted by a strikethrough of the name. Click the name again to include.

Issues Over Time

Issues by Severity

Issues by Reference

You can export the dashboard data as a CSV for reporting, sharing, or deeper analysis outside of Epsilon3.