Index Issue Specifications
Last updated
Last updated
We use "index" Github issues to centralize information about each of our projects and products. It is critical that these issues follow a standard labeling scheme and content format so that is accurate, team members work is coordinated and efficiently tracked, and we have an accessible, high-level view of the project/product on the .
All projects which have been scoped require a project index issue to be placed in the appropriate Zenhub pipeline. The issue title, description, and labels should follow the below guidelines.
The issue title should be prefixed with Project: . For example, Project: Warehouse Inventory Management.
Project Index
Project: xzy — A project-specific label that you will create, following our
Workgroup: xyz — the project stakeholder workgroups
All DTS team members who contributed substantially to the project, including at least one product manager or team lead.
Follow the issue template.
See Index Issue Images below.
All products require a product index issue to be placed in the appropriate Zenhub pipeline. Once a product has been released, it should be placed in the Ongoing pipeline indefinitely until it is removed from service. The issue title, description, and labels should follow the below guidelines.
The issue title should be prefixed with Product: . For example, Product: Data Tracker
Product Index
Workgroup: xyz — the workgroup(s) of the product's primary users
The product manager.
See Index Issue Images below.
All projects and products should have at least one image so that missing thumbnails don't disrupt the website design. We prefer these thumbnails options:
Please avoid using
Vendor logos - these doesn't give any information about the platform or use case and promote a commercial companies
Product: xzy — A product-specific label that you will create, following our
Follow the issue template.
A or other of the data generated in the app
Photos of the project/product's or the related /; the is a fantastic source for these. We also have a you can add to or use.
A
For mobile-focused apps, we have a to show off ​
Full-screen screenshots or large diagrams as the first image - these don't render well in tiles. if they are helpful way to communicate the work.
The image should be at least 1000px wide, with a 3:2 aspect ratio. makes it easy to crop/resize as needed.