Workflow for Software Development Tasks and Issues

Home » Policy and Procedure » Workflow for Software Development Tasks and Issues
Policy and Procedure No Comments

This shows the workflow using JIRA.

Issuer – Person creating the jira issue/task. Typically, it’s the Customer Support that raises issues.

Developer – developers assigned to the task

Release Manager – responsible for integrating the correct branch and release to test environment.

QA (Quality Control) – responsible for verifying the issue is fixed and then close the issue


Workflow

  1. Issuer will create an OPEN jira issue and assign to the Developer
  2. Developer will investigate and fix the assigned problem
  3. Once it’s fixed, Developer marks the jira issue to be RESOLVED and then assign the issue to the Release Manager
  4. Release Manager to merge the code and do some preliminary integration testing.
  5. Release Manager will deploy the fix in the test environment
  6. Release Manager will assign the issue to QA
  7. QA will verify the issue is addressed, reopen and reassign the issue back to the developer if needed
  8. If Test is successful QA will add a comment and re-assign the JIRA back to the Release Manager to update the customer.
  9. Once customer’s version is updated, Release Manager will re-assign issue to QA to verify in production.
  10. If this issue is first raised by a customer, Customer Support will inform the customer of the fix.