arrow-left

All pages
gitbookPowered by GitBook
1 of 1

Loading...

Index Issue Specifications

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 DTS' project dataarrow-up-right is accurate, team members work is coordinated and efficiently tracked, and we have an accessible, high-level view of the project/product on the DTS Websitearrow-up-right.

circle-info

Create a new Project or Product Index by selecting the appropriate issue templatearrow-up-right from the atd-data-techGithub repository.

hashtag
Project Index

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.

hashtag
Title

The issue title should be prefixed with Project: . For example, Project: Warehouse Inventory Management.

hashtag
Labels

  • Project Index

  • Project: xzy — A project-specific label that you will create, following our

  • Workgroup: xyz

hashtag
Assignees

All DTS team members who contributed substantially to the project, including at least one product manager or team lead.

hashtag
Description

Follow the issue template.

hashtag
Image

See below.

hashtag
Product Index

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.

hashtag
Title

The issue title should be prefixed with Product: . For example, Product: Data Tracker

hashtag
Labels

  • Product Index

  • Product: xzy — A product-specific label that you will create, following our

  • Workgroup: xyz

hashtag
Assignee

The product manager.

hashtag
Issue description

Follow the issue template.

hashtag
Image

See below.

hashtag
Index Issue Images

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:

  • 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

Please avoid using

  • 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.

  • Vendor logos - these doesn't give any information about the platform or use case and promote a commercial companies

The image should be at least 1000px wide, with a 3:2 aspect ratio. makes it easy to crop/resize as needed.

— the project stakeholder workgroups
— the workgroup(s) of the product's primary users

For mobile-focused apps, we have a to show off ​

project label conventionsarrow-up-right
Project Indexarrow-up-right
product label conventionsarrow-up-right
Product Indexarrow-up-right
maparrow-up-right
visualizationarrow-up-right
end users at workarrow-up-right
hardwarearrow-up-right
servicearrow-up-right
TPW Flickr feedarrow-up-right
stash of nice photosarrow-up-right
close-up screenshot of a unique part of the UIarrow-up-right
Include these later on in the issuearrow-up-right
This toolarrow-up-right
Index Issue Images
Index Issue Images
templatearrow-up-right
the application on different devicesarrow-up-right