Knowledge Base

On this page most information about the Capturum Software Group is found in a central place. This so you can read and find the information here whenever you need it.

This document is being filled continuously . So if you are missing any information please don’t hesitate to ask.

Internal tickets:

Story – Userstory, defined functionality part of the initial scope
Task – Tasks to be performed by development team
Test Result – Results found by internal testing
Improvement – Additional functionality part of an existing feature, not part of the initial scope
Technical improvement – Sentry issues and other technical dept or improvements. Tickets made by development
New feature – New feature, not part of the initial scope
Epic – Epics can be used to group multiple tickets of the above types to group them easily. When creating an Epic set the state to ‘Hour registration’ to prevent them from messing up the Jira boards.
Hour logging – Tickets to register hours not directly related to a single task or story.

Client tickets:

Bug – When a client reports a bug is when the ‘Bug’ type is used. These ‘Bugs’ are faults reported by the client.
Hotfix – When a bug is blocking the clients daily processes it may be marked as a “hotfix” and developed individually. The projectmanager is the one changing ‘bugs’ to ‘hotfixes’ after consultation with client and/or their lead developer.

Testing tickets:

With XRAY implemented in Jira our QA can create tickets with one of the following types:
Test, Test Set, Test Plan, Test Execution, Precondition. These tickets and types are free to be used by QA