8000 Create a Mock Video to instruct common kanban tagging mistake · Issue #916 · hackforla/website · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Create a Mock Video to instruct common kanban tagging mistake #916
Open
@pawan92

Description

@pawan92

Overview

We need a mock video of a person creating an issue and assigning the wrong tags.

More detail

According to the "How to use the Kanban board document", adding the front end tag to an issue because it will eventually need front end support is not the correct way to use a tag. Instead, the tag should be assigned once it is at that stage. This is helpful so that issues can be filtered and assigned quickly & accurately

Action Items

  • Review "Common Kanban mistakes" in this document which this comment is addressing.
  • Create a video of making an issue (using template below)
    • Add issue to the project board
    • Add labels to the issue in the video
      • p-feature label (p-feature: SDG page)
      • Size label (size: 1pt)
      • and all role labels (which is a no-no) and then reducing back to just the first role label required in the fake issue (role: product).
  • Adapt cover page from Guide template to coverpage for video.
    • Get Bonnie to add you to the Guides Team figma
    • Add to video
    • Review with Product

Resources/Instructions

Text to copy for when you are writing your mock issue

### Overview
Create SDG page to be added to Hack for La website

### Action Items
- [ ] Product
   - [ ] ideate
   - [ ] define feature requirements
   - [ ]  make issues for UI/Development
      - [ ] Design
        - [ ] design the mockup
        - [ ] get feedback from Product
     - [ ] Front-end
        - [ ] develop according to Figma

### Resources
[Figma File](https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    New Issue Approval

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0