Build

An issue is a type of work that requires updates to a part (product/service). These must be created or accepted by someone who has a role on a part (such as a part owner, part dev, or part provider).

Issue management

DevRev has two ways of managing issues: Now, Next, Later (NNL) for ongoing development with the Kanban methodology; and sprints with specified date ranges to support the scrum methodology.

Both types can coexist within a dev org, and you can view issues assigned to a sprint on a sprint board. NNL is the default mechanism in DevRev. If you want to use sprints, you can configure a product or capability to have a sprint board.

Issue

An issue may be created by a dev user with a role on associated part or through automation.

Tags [values]:

• Stalled
• Priority/Escalated
• Fast/Slow Moving
• Blocked
• Resolution: [values]
• Impact: [values]
• Reason: [values]

An autonomous issue is an issue created automatically from an external event, such as a new VCS branch or pull request. These issues have the tag autonomous.

Stages

The following figure shows the state machine for issues.

Open

• Triage

  Issues that are newly created. From here either a user or automation will take a look at the issue and make a determination of where it should go. In certain cases it may be immediately closed as a duplicate if the reported concern already exists in another issue. In other cases, the owner may determine that the issue is invalid or will not be fixed for other reasons and will close the issue as won't fix.

  If the issue is not a duplicate and is something that should be accepted, the dev will determine how soon it should be addressed by moving into the backlog, next, or now stage.

• Backlog (later)

  Issues that have been accepted but aren't planned for the next few development cycles (next and now). Issues in the 'backlog' stage may move directly to next or now depending on the current priority.

• Next

  Issues that are not part of the current development cycle but are planned to be completed in the subsequent cycle. Issues in the next stage should have clear requirements definition. Issues in the next stage may be prioritized (promoted to now) or deprioritized (demoted to backlog).

• Now

  Issues that are planned to be completed in the current development cycle but which have not yet been started. When an issue starts to be worked on it will move to the in development stage. Issues in the now stage should have clear requirements definition. Issues in the now stage may be deprioritized (demoted to 'backlog' or 'next')

In-progress

• In development

  The issue owner is actively working on the issue. When the owner has their resolution in a good state they will request review which will put the issue in the in review stage.

• In review

  The issue and resolution are currently being reviewed. In certain scenarios the reviewer may request changes to the proposed solution. In this scenario, the stage would transition back to in development. If the reviewers approve the fixes, the issue will progress into the in testing stage for validation.

• In testing The fixes have been approved and are currently undergoing validation. If the tests fail or bugs are made apparent, the issue will transition back to the in development stage as changes are required. If the tests pass and the fix is acceptable, the issue will start the deployment (CD) lifecycle and transition into the in deployment stage.

• In deployment The fixes are currently being deployed. When the deployment is complete, the issue will transition to the resolved stage. Traditional CD processes may move changes through various environments. These transitions should be tracked with stage notes.

Closed

• Won't fix

  Will not be addressed with a change to the product.

• Duplicate

  Redundant with some other issue.

• Resolved

  Deployment is complete.

Create an issue

1. Go to Build > Issues from the sidebar on the left.

2. Click New Issue on the-top right corner of your screen.

3. Add a title and description for your new issue. You can also attach files related to the issue in the description.

4. Select which part of the company/product this issue is related to.

   

5. Enter other attributes for the issue: change the assignee or accept the default; enter the severity; add any relevant tags to help employees identify any relevant traits of the issue; select the rev org that the issue pertains to.

6. If there are other tickets or issues that relate to this issue, click Link Records and select the relevant items.

7. If you would like to immediately create another issue, select Create multiple.

8. Click Create.