Managing Requirements
Managing Requirements
Creating a New Requirement
To add a brand-new requirement to a specification:
Right-click on an existing requirement row (or on the empty table area if the specification is empty).
Choose Create Requirement from the context menu.
Fill in the fields in the dialog that appears:
Summary (required) — the title of the requirement
Description (optional)
Any additional fields configured for your requirement issue type
Click Create to confirm.
The app creates a new Jira issue and adds it to the specification immediately after the row you right-clicked.
Adding an Existing Jira Issue as a Requirement
If you already have a Jira issue that you want to include in a specification without creating a duplicate:
Right-click on a requirement row to set the position.
Choose Add Existing from the context menu.
Search for the issue by key or summary in the dialog that appears.
Select it and confirm.
The issue is added to the specification at the chosen position. The original Jira issue is unchanged.
Organising Requirements (Hierarchy and Order)
Requirements within a specification can be nested to show relationships — a requirement can be a parent with child requirements beneath it. This is useful for breaking down a high-level requirement into more specific ones.
Moving Requirements Up and Down
Right-click a requirement and choose Move Up or Move Down to change its position among requirements at the same level.
Indenting and Outdenting (Creating Parent-Child Relationships)
Indent (make a child): Right-click a requirement and choose Indent. The requirement moves one level deeper and becomes a child of the requirement directly above it.
Outdent (promote): Right-click a requirement and choose Outdent. The requirement moves one level up, becoming a sibling of its former parent.
ℹ️ Note: When you move or restructure requirements, the app automatically updates all related paths and links in the background. You do not need to do anything extra.
Copy, Paste, and Reuse Requirements
You can copy a requirement from one location and paste it somewhere else — either as a brand-new copy, or by reusing the same Jira issue in multiple places.
To copy and paste:
Right-click the requirement you want to copy and choose Copy.
Right-click the target requirement (where you want to paste) and choose Paste.
The Paste Options dialog appears.
Paste Type
Choose how you want to paste the requirement:
Option | What happens |
|---|---|
Copy Requirement | Creates a new Jira issue with the same summary, description, assignee, priority, and configured custom fields as the original. A new requirement entry pointing to this new issue is added to the specification. |
Reuse Requirement | No new Jira issue is created. Instead, a new specification entry is added that points to the same Jira issue as the original. Useful when the same requirement applies to more than one specification. |
Paste Position
Choose where to place the pasted requirement relative to the one you right-clicked:
Option | What happens |
|---|---|
Place After | The pasted requirement is inserted as a sibling — at the same level, directly after the selected requirement. |
Place Below | The pasted requirement is inserted as a child — one level deeper, under the selected requirement. |
Copying with Hierarchy (Children Included)
Check With Hierarchy to copy the full subtree of children along with the parent.
In Copy mode: every child in the tree gets its own new Jira issue.
In Reuse mode: new specification entries are created for each child, all pointing to the original Jira issues.
ℹ️ Note: When copying large hierarchies, the app processes items one at a time and shows a progress indicator. This may take a moment for deep trees.
Bulk Operations
To work on multiple requirements at once:
Hold Shift and click to select multiple rows.
Right-click to open the context menu.
Choose Bulk Edit to update a field across all selected requirements at once, or Delete to remove multiple requirements in one action.
Right-Click Context Menu Reference
Here is the full list of actions available when you right-click a requirement row in the table:
Action | Description |
|---|---|
Create Requirement | Create a new Jira issue and add it as a requirement after this row |
Add Existing | Link an existing Jira issue as a requirement |
Copy | Copy this requirement (and optionally its children) for pasting elsewhere |
Paste | Paste a previously copied requirement, with options for copy or reuse |
Edit Properties | Open the properties panel to edit this requirement's fields inline |
Move Up / Move Down | Shift this requirement up or down among its siblings |
Indent | Make this requirement a child of the one directly above it |
Outdent | Promote this requirement one level up in the hierarchy |
Add Link | Create a Jira issue link from this requirement to another issue |
View Comments | Open the comments panel for this requirement |
View History | Open the change log for this requirement |
Baselines | Create or view named snapshots of this specification |
Delete | Remove this requirement from the specification (the Jira issue itself is not deleted) |
Export and Import (XLSX)
The requirements table can be exported to Excel and re-imported to make bulk updates or to onboard requirements from a spreadsheet.
Export: Click the export option in the toolbar or context menu. The app downloads an XLSX file containing all requirements in the current specification, with all visible columns.
Import: Click the import option and upload an XLSX file. The app reads the column mappings configured in Settings to match spreadsheet columns to Jira fields and adds or updates requirements accordingly.