Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add planning board to triage party!! #269

Open
wants to merge 13 commits into
base: master
Choose a base branch
from

Conversation

tejal29
Copy link
Contributor

@tejal29 tejal29 commented Jun 10, 2021

New feature to add a planning board to triage party.

Features supported:

  1. Categorize issues per themes or OKRs for a quarter. In the screen shot, Skaffold themes for planning cycle are "Performance", "Events API" and then partner issues.
  2. Display, all issues which are not planned in any milestone in "Not Planned" row.
  3. Display all planned issues in the milestone they belong to.
  4. Show all in progress tasks with information like,
    • the milestone they belong to
    • the PRs attached to them.
      This has also let the team surface issues which were part of past milestones but not completed.

image

Sample config for the planning board!

  1. Define the themes or columns for the planning view.
- id: planning
    name: Planning
    description: >
      Skafold Team Planning Board.

      This board is used by Skaffold team to plan upcoming releases.
      The timeline and priority of issues listed here are subject to change.

    display: planning
    overflow: 3
    rules:
      - performance
      - event-api-v2
      - partner-requests
      - all-other-requests
  1. Define individual rules for these themes.
  ## Planing
  performance:
    name: "Performance issues"
    type: issue
    filters:
      - label: "planning/Q2-21"
      - label: "area/performance"

  event-api-v2:
    name: "Output/ Event API v2"
    type: issue
    filters:
      - label: "planning/Q2-21"
      - label: "area/api_v2"

  partner-requests:
    name: "Other partner requests"
    type: issue
    filters:
      - label: "planning/Q2-21"
      - label: "source/partnerships"

  all-other-requests:
    name: "Others"
    type: issue
    filters:
      - label: "planning/Q2-21"

Another view from past with multiple milestones.
image

@tejal29 tejal29 force-pushed the add_planning_board branch from 2b9fb83 to f777ff7 Compare June 10, 2021 23:19
@tejal29 tejal29 requested a review from gsquared94 June 11, 2021 16:23
@tstromberg
Copy link
Collaborator

Wow, this looks like a very interesting change.

pkg/site/planning.go Show resolved Hide resolved
config/examples/skaffold.yaml Outdated Show resolved Hide resolved
pkg/site/kanban.go Outdated Show resolved Hide resolved
pkg/site/planning.go Outdated Show resolved Hide resolved
pkg/site/planning.go Outdated Show resolved Hide resolved
site/planning.tmpl Outdated Show resolved Hide resolved
@tstromberg
Copy link
Collaborator

Nice work! I've added some minor feedback items.

Could you also update the documentation to describe the intent/usage of the planning board?

@tejal29
Copy link
Contributor Author

tejal29 commented Jun 16, 2021

Thanks for the review! Will try to address this this week!

@tejal29 tejal29 force-pushed the add_planning_board branch from ab49da2 to b382f5c Compare June 25, 2021 18:59
![planning mode](docs/images/planning.png)

In v1.5.0, pages can now be displayed as a SCRUM dashboard.
The columns are based on the feature or Objective(O) the issue belongs to. Use rules to define features.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about 'objective' instead of 'Objective(O)'?

## Planning Board mode (NEW)
![planning mode](docs/images/planning.png)

In v1.5.0, pages can now be displayed as a SCRUM dashboard.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe Scrum is the correct capitalization


In the above example, skaffold has 2 Objectives and 2 features defined
The two objectives are
1) Simply onbaording and make inner devloop faster
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can remove these two lines

@joeyparrish joeyparrish added the enhancement New feature or request label May 26, 2022
@joeyparrish
Copy link
Member

Hi @tejal29,

As @tstromberg is no longer at Google and nobody else was active on the project, I've been made a maintainer. Please let me know if you'd like to revive this PR. I'm a user of Triage Party, but only of the Collections view. As I'm new to the codebase, if we revive this PR, I may need to discuss the changes with you in more detail so you can help me understand everything.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants