Related Stories Tab

The Related Stories tab links branches with external systems like Jira, showing connected stories with priority, status, and assignee to keep development aligned with project tracking.

When you create a branch, you can link it to stories from an integrated project management tool such as Jira. These stories will automatically appear in the Related Stories tab. You can also add or manage stories manually from this tab, keeping the branch tied directly to the work it represents. The Related Stories tab provides a direct bridge between code and project management, ensuring that development work is always connected to its business context.

Adding Stories

Stories can be linked to a branch in two ways:

• At branch creation: Select the integration (e.g., Jira), choose the project, and pick one or more stories. These will be automatically added to the Related Stories tab.

• From the Related Stories tab: Use the Add stories button to link new stories at any time. You must select the integration, project, and at least one story to add.

Fields Explained

Each story entry displays the following fields:

• Integration Name – The external system the story comes from (e.g., Jira).

• Issue Key – The unique identifier of the story (e.g., FLOS-23).

• Priority – Importance level of the story (e.g., Low, Medium, High).

• Status – Current stage of the story (e.g., Backlog, Selected for Development, In Progress).

• Fix Versions – Release or target version tied to the story (e.g., Feature, HotFix, QA).

• Assignee – The team member responsible for completing the story.

• Summary – A short description of the story (e.g., “Working on Veeva User Story Feature1”).

Important Notes:

• A single branch can be linked with multiple user stories from Jira (or another integration).

• If a story is no longer relevant, it can be unlinked from the branch by clicking the delete (trash) button next to it.

Use Cases

• Ensure every branch is connected to business requirements for traceability.

• Track which stories are under development directly from the branch view.

• Filter stories by priority or assignee for quick navigation.

• Manage scope by adding or removing related stories as work evolves.

Best Practices

• Always link at least one story when creating a new branch to ensure alignment with project tracking.

• Keep story priorities and statuses updated in Jira so the Related Stories tab reflects accurate progress.

• Use the summary field as a quick check to confirm whether the branch is aligned with the right feature or fix.