Documentation (Jira and Tickets)#

For detailed information on the Jira process, review the Jira process document.

For all new features, bug fixes, missing functionality, and enhancement tickets, if there are no existing specs, developers are required to provide a brief document outlining:

How the requirements will be met.
The proposed technical approach.
Any research or analysis findings.
Potential impact (module-specific or system-wide).

Kanban process flow#

The developer Kanban workflow contains seven stages:

For Development → In Progress → On Hold → To Test → Testing → Ready to Merge → Publish

In Progress#

Move actively worked tickets to In Progress. After reviewing the task, enter the estimated effort in the Estimation Time field.

Record the time spent in the Work Log field.
Add detailed progress comments and any task-related questions.
Before handing off the ticket, complete the developer checkpoints.

Testing#

Test the feature.
Prepare handoff documentation for QA.
Move the ticket to To Test and assign the QA owner.
Include clear steps, screenshots, and a description of the fix. Example.

On Hold#

When another ticket takes priority, move the current ticket to On Hold and explain the reason in a comment. The priority number appears at the bottom of the ticket overview.

Ready to Merge#

After QA verifies the change, the ticket moves to Ready to Merge. Merge the feature branch into DbChanges_Staging and any other branches identified by the ticket’s Fix Version/s field.

Publish#

After a successful merge, move the ticket to Publish.

Ticket issue analysis#

Before starting development, read the ticket description and comments to determine whether the ticket is new or was previously rejected.

For a rejected ticket, search the Git history using the ticket number to find prior work.