Setting Up the App (Settings)
Setting Up the App
Settings control how NewSysRS Requirements for Jira works for your project. Each project has its own independent settings, so changes you make here only affect the project you currently have selected.
To open settings, click Settings in the left sidebar.
Settings are divided into three tabs:
Specifications — how specification documents are configured
Requirement — how individual requirements are configured
Reviews — how the review workflow is configured
⚠️ Important: You must complete at least the Specifications and Requirement tabs before anyone on the team can use the app. Review settings are only needed if you plan to use the Reviews module.
Specification Settings
Go to: Settings → Specifications
A specification is a document that groups and organises a set of requirements. Think of it like a chapter in a requirements document — it has a title, lives in a folder, and contains a list of ordered requirements.
Behind the scenes, each specification is an ordinary Jira issue of a type you choose (for example, an Epic or a custom issue type your team has created). This means specifications show up in Jira like any other issue and benefit from Jira's existing workflows.
Field | Required | Description |
|---|---|---|
Issue type for Specifications | Yes | Choose the Jira issue type that will represent specification documents. This is often "Epic" or a custom type such as "Specification". |
Field for Specification Type | No | If your specification issue type has a dropdown or radio-button field that categorises the type of specification (e.g. "Functional", "Non-Functional"), select it here. The app will use its values as artifact types. |
Artifact Types
If you configure the Field for Specification Type, each option in that field becomes a configurable artifact type. For each artifact type, you can choose which custom fields from the specification issue type appear as columns in the requirements table.
This is useful when different types of specification documents need to show different columns.
Click Save when done.
Requirement Settings
Go to: Settings → Requirement
A requirement is a single Jira issue that represents one specific need, behaviour, or condition. Requirements live inside specifications and are the core items you will be creating, reviewing, and tracing throughout the app.
Like specifications, each requirement is an ordinary Jira issue — it has a key, summary, status, assignee, and any custom fields your team uses.
Field | Required | Description |
|---|---|---|
Issue type for Requirements | Yes | Choose the Jira issue type that will represent individual requirements (e.g. "Story", "Task", or a custom type). |
Field for Requirement Type | No | If your requirement issue type has a type-categorisation field, select it here for filtering and column configuration. |
Custom field mappings | No | Choose which custom fields from the requirement issue type appear as editable columns in the requirements table. |
Click Save when done.
Review Settings
Go to: Settings → Reviews
The Reviews module lets you run formal, structured reviews of requirements. Before it can be used, you need to tell the app which Jira issue types and link types to use for the review process.
Field | Required | Description |
|---|---|---|
Issue type for Review | Yes | The Jira issue type used to create the parent review issue (e.g. "Review" or "Epic"). This must be a standard issue type, not a sub-task. |
Issue type for Reviewers | Yes | The Jira issue type used to create one sub-issue per reviewer (e.g. "Sub-task"). Each reviewer in a review gets their own Jira issue so their progress can be tracked individually. |
Link type for Requirements | Yes | The Jira issue link type used to connect requirements to a review issue (e.g. "is reviewed by"). |
Default Review description | No | A default text that pre-fills the description field whenever a new review is created. Useful for review templates or standard instructions. |
Review Fields | No | Select which custom fields from the Review issue type should appear in the review creation and editing form. Only fields you list here will be visible. |
Reviewer Fields | No | Select which custom fields from the Reviewer issue type should appear on each reviewer's sub-issue. |
Attribute Rules | No | Set up automatic rules that update a requirement's field value when a review reaches a certain status. For example: automatically set a requirement's "Approval Status" field to "Approved" when the review is closed. See the Attribute Rules section on Page 6 for more detail. |
Click Save when done.