Skip to content

How to file NDS work request

Jump to bottom
Nikola Pejcic edited this page Oct 12, 2023 · 16 revisions

NDS work requests

NDS work requests are collected and monitored in GitHub Issues.

Types of requests

There are 4 types of requests:

  • Bug report » "I found a problem with NDS"
  • Feature request » "I need new functionality/behaviour added to an existing component or a new component"
  • Support request » "I need help or consultation"
  • Miscellaneous request » "I don’t know how to classify this request"

Process

After filing the ticket Design Ops group with review the request within 1 business day and get back with a plan for execution or an alternative proposal.

The execution of work requests is not limited to Design Ops and anybody is able to execute open work requests. When filling a request you will be asked to specify if you want to work on the issue or if you would prefer Design Ops to work on it.

If you decide to work on the request yourself, someone from Design Ops will review and assign the request to you. Make sure the request has been assigned to you before starting to work on it to prevent duplication of efforts and the introduction of undesirable components, functionalities, or behaviors.

If you are relying on Design Ops for completion of the request please refer to the table below for estimated first response and completion time. Please note that these are estimates and that the actual completion date is affected by the complexity of the request and its priority.

Last updated: Oct-12-2023

First response Completion
Bugs End of day 5 days
Feature request 1 business day 20 business days
Consult 1 business day 10 business days

Common scenarios

1. You found a bug and want to fix it yourself

  1. You submit a bug fix request indicating that you want to fix it (status: triage)
  2. Design Ops confirms that the bug indeed exists (status: open), or that it doesn’t (status: closed)
  3. You fix the bug (status: in progress)
  4. You submit a PR when completed (status: in review)
  5. Design Ops or you merge fix/release (status: completed)

2. You found a bug and want DesignOps to fix it

  1. You submit a request (status: triage)
  2. You monitor request status change (status: closed, open, in progress, in review, completed)

3. You want to enhance the functionality or behaviour of an existing component or build a new component

  1. You align with designer on your team on the requirements
  2. You submit a Feature request indicating that you want to work on it (status: triage)
  3. Design/Design Ops decide if new component/functionality should be included in NDS or be local to your application (status: open, closed)
  4. You execute work (status: in progress)
  5. You submit a PR when completed (status: in review)
  6. Design Ops or you merge fix/release (status: completed)

4. You want DesignOps to enhance the functionality or behaviour of existing components or build a new component

  1. You submit a request (status: triage)
  2. You monitor request status change (status: closed, open, in progress, in review, completed)

5. You want to consult or need support with anything NDS-related

  1. You submit a request (status: triage)
  2. You will be contacted by Design Ops with a proposal (status: open, closed, in progress, completed)

6. Miscellaneous request

  1. You submit a request (status: triage)
  2. You will be contacted by Design Ops with a proposal (status: open, closed, in progress, completed)

Monitoring the progress of work requests

The best way to see the progress of work requests is through board or table view of the NDS work request project.

Clone this wiki locally