• Created by Unknown User (fay), last modified on Feb 02, 2017

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

How to Propose a New Feature

<<TO DO: update this "propose a new feature" process more explicit (and correct it if wrong) >>

  1. Query the existing list of issues to see if the new idea has already been proposed.
  2. Create a story and add it to the backlog for the specific project
  3. The project leader will accept, reject, and/or modify the proposal, and update its state, accordingly.

Workflow for Reporting Bugs and Updating Their Status

The PowerPoint presentation Jira Bug Flow v2.pptx documents the life cycle of a bug report. Here is the workflow:


Definition of Bug Report States

Specific Bug Report Use Cases

The document Jira Bug Job Aid - v3 describes, for specific use cases, how to submit and update bug reports and issues within JIRA. Here are the use cases currently described in that document

  • Bug: Use Case 1: Test originated bug, Code fix provided, Retest successful
  • Bug: Use Case 2: Test originated bug, Code fix provided, Retest Failed

<<TODO: are there more use cases to describe?>>

Workflow for Applying a Fix to the Source Code

<<TODO: improve or correct the following description of the workflow for applying a fix to the source code>>

  1. Reporter reports the issue, assigns to self to fix.
  2. Submits fix to Gerrit, Gerrit is integrated with Jira, so you can follow status of submission - Gerrit has it's own status to know when something is accepted/approved/merged..
  3. We have a couple of options with Jira…
    1. Create a Submit state
    2. Or if using default workflow; add Resolution tag so that we can show Jira as In Progress/Submitted.
    3. Once Gerrit review passes and is accepted, merged, JIRA ticket is moved to Resolved/Fixed (Bug) or Resolved/Implemented (story) - we need to finalized these workflows
  • No labels