# Fixing issues
Fixing issues identified by seatbelt is easy. Once a given rule has executed, you will be able to see the output of the queried result of your rule. Rules that are designated as warnings or errors generally succeed if no results are returned, and fail if any results are returned. Any rule that returns results (whether info, warning, or error) will be clearly marked. Each failure may indicate that a certain field value is missing or has incorrect data. You can see the list of erroneous records by clicking on the rule. If this is the very first time running Seatbelt on a long-running project, it is possible that there may be a long list of erroneous records, but if you run Seatbelt regularly, there will likely be few if any records returned. You can navigate to Jira issue, sprint, board, version, or project to fix the issue found with your rule by clicking on the link. Conceptually the process of addressing these issues found by seatbelt is very much like to how you would use a Jira filter in Jira issue navigator to find issues and navigate to their details.
# Steps
- Identify which field need to be updated, in order for Seatbelt rule to pass.
Let's assume we have a rule to capture
issue without epic
, when rule catches any result then the issue shown on the result page requires your team member to update this issue by addingepic
.
- Navigate to the detail page of Jira data (boards, issues, sprint, project, versions)
Navigating is much like your Jira filter GUI, simply click the
key
data from the result row.
- Update the data.
Continuing with the example of a result found from the rule that captures
issues without epic
the fix is to assign anepic
to this issue. Once the data is updated on Jira, the next time Seatbelt runs it will no longer include this record in the list of errors.