Jira - Local help - Stationeers Bug Database

Jira tracks issues, which can be bugs, feature requests, or any other tasks you want to track.

Each issue has a variety of associated information including:

the issue type
a summary
a description of the issue
the project which the issue belongs to
components within a project which are associated with this issue
versions of the project which are affected by this issue
versions of the project which will resolve the issue
the environment in which it occurs
a priority for being fixed
an assigned developer to work on the task
a reporter - the user who entered the issue into the system
the current status of the issue
a full history log of all field changes that have occurred
a comment trail added by users
if the issue is resolved - the resolution

Issue Types

Jira can be used to track many different types of issues. The currently defined issue types are listed below. In addition, you can add more in the administration section.

For Regular Issues

Task: A task that needs to be done.
New Feature: A new feature of the product, which has yet to be developed.
Bug: A problem which impairs or prevents the functions of the product.
Story: Created by JIRA Software - do not edit or delete. Issue type for a user story.
Improvement: An improvement or enhancement to an existing feature or task.
Epic: Created by JIRA Software - do not edit or delete. Issue type for a big user story that needs to be broken down.

For Sub-Task Issues

Sub-task
Sub-bug

Priority Levels

An issue has a priority level which indicates its importance. The currently defined priorities are listed below. In addition, you can add more priority levels in the administration section.

Critical: This problem will block playing the game.
Major: Serious problem will block progress.
Moderate: This issue could affect progress.
Minor: Minor problem or easily worked around.
Trivial: Very small or cosmetic problem, does not affect playing the game.

Statuses

Each issue has a status, which indicates the stage of the issue. In the default workflow, issues start as being Open, progressing to In Progress, Resolved and then Closed. Other workflows may have other status transitions.

Open: The issue is open and ready for the assignee to start work on it.
In Progress: This issue is being actively worked on at the moment by the assignee.
Reopened: This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved.
Resolved: A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.
Closed: The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.
To Do: This issue is open and is waiting for development.
In Review: The issue has been fixed and is being retested in the build.
Done: Work on this issue has been Done. This is an old Resolution that is kept because of old issues. Please do not use on Jira Cloud.
Investigate: This issue is being investigated by the development team.
Awaiting Development: This issue is waiting to be picked up by the programming team.
Blocked: Progress on this issue is being blocked by another issue. Please link the Blocking issue.
Building: Source code has been committed, and JIRA is waiting for the code to be built before moving to the next status.
Build Broken: The source code committed for this issue has possibly broken the build.

Resolutions

An issue can be resolved in many ways, only one of them being "Fixed". The defined resolutions are listed below. You can add more in the administration section.

Done: This issue was fixed.
Cannot Reproduce: All attempts at reproducing this issue failed, or not enough information was available to reproduce the issue. Reading the code produces no clues as to why this behavior would occur. If more information appears later, please reopen the issue.
Duplicate: The problem is a duplicate of an existing issue.
As Designed: This issue is intended design decision.
Won't Do: This issue won't be actioned.
User Error: The issue is deemed as not a bug but could still be considered problematic. For example, user errors end up in this resolution.
Fix Deployed: The issue is considered to be finished and has been deployed to the build.