#8 drag-n-drop issue tracker for JoystreamStats

Aberto
há 3 anos atrás aberto por l1dev · 2 comentários

$450

isonar set up trello for task management because of the possibility to drag items to change its priority.

we need this functionality in-house to adjust it to our needs:

  • list all tasks from different places
  • let members change priority
  • member can self-assign (task moves from backog to in progress)
  • lead can change status
  • submit changes to API backend

data

show

we can either find a way to store them in one place or add references the backend.

model

task {
  id: number;
  funded: number;
  priority: number;
  status: string;
  title: string;
  type: string;
  url: string;
}

Member.hasMany(Task)
Task.hasMany(Member, {as: `assignee`})
Task.belongsTo(Member, {as: `creator`})

swimlanes

  • fetch list of issues
  • display them in columns based on status
  • drag-n-drop to change priority (track and display changes)

t-shirt budgeting

T-shirt sizing and monetary value one additional parameter will make a lot of sense: Community value. This can be also measured in T-shirt sizes: S, M, L, XL and would indicate how important this task is for the community and how much the community will benefit from it. If the task automates the daily routine of one man, it has a community value of XXS 

But when the entire community is positively impacted, its XXXL 

Having these three dimensions: Complexity value, Community value and the budget, it's easy to prioritise the backlog and deliver the maximum value.

comments, self-assign

  • comments per issue
  • assign self or someone else
*$450* - Proposal: https://joystreamstats.live/proposals/417 - Branch: https://git.joystreamstats.live/Operations/jsstats/src/frontend-tasks isonar set up trello for task management because of the possibility to drag items to change its priority. we need this functionality in-house to adjust it to our needs: - [ ] list all tasks from different places - [ ] let members change priority - [ ] member can self-assign (task moves from `backog` to `in progress`) - [ ] lead can change status - [ ] submit changes to API backend # data show - [git issues](https://git.joystreamstats.live/Operations/process/issues) - [bounties](https://joystreamstats.live/bounties) - KPI (https://git.joystreamstats.live/Operations/process/issues/38) we can either find a way to store them in one place or add references the backend. ## model ``` task { id: number; funded: number; priority: number; status: string; title: string; type: string; url: string; } Member.hasMany(Task) Task.hasMany(Member, {as: `assignee`}) Task.belongsTo(Member, {as: `creator`}) ``` # swimlanes - fetch list of issues - display them in columns based on status - drag-n-drop to change priority (track and display changes) # t-shirt budgeting T-shirt sizing and monetary value one additional parameter will make a lot of sense: Community value. This can be also measured in T-shirt sizes: S, M, L, XL and would indicate how important this task is for the community and how much the community will benefit from it. If the task automates the daily routine of one man, it has a community value of XXS  But when the entire community is positively impacted, its XXXL  Having these three dimensions: Complexity value, Community value and the budget, it's easy to prioritise the backlog and deliver the maximum value. # comments, self-assign - comments per issue - assign self or someone else
l1dev comentado há 3 anos atrás
Proprietário

@isonar, suggested a SCRUM process:

  • Tasks are prepared by Council (frontend login)
  • added to the backlog (RESTful db)
  • prioritized (users vote priority)
  • estimated in days and $$$ by the Ops team (task.price)

But then the most interesting part happens: finding a balance between business value of the task and its cost. Usually, if the backlog is prioritised, top items indicate top priority. However, team may estimate top items very high, and the Council will have to make a choice: which tasks it can afford and which - it can't.

more

@isonar, [suggested](https://pioneer.joystreamstats.live/#/forum/threads/531?replyIdx=3) a SCRUM process: - Tasks are prepared by Council (frontend login) - added to the backlog (RESTful db) - prioritized (users vote priority) - estimated in days and $$$ by the Ops team (`task.price`) > But then the most interesting part happens: finding a balance *between business value of the task and its cost. Usually, if the backlog is prioritised, top items indicate top priority. However, team may estimate top items very high, and the Council will have to make a choice: which tasks it can afford and which - it can't.* [more](https://pioneer.joystreamstats.live/#/forum/threads/531?replyIdx=3)
isonar comentado há 3 anos atrás
Colaborador

I strongly advise to not spend a dime on creating custom ticket management solution and just use off-the-shelf ones instead.

I strongly advise to not spend a dime on creating custom ticket management solution and just use off-the-shelf ones instead.
Faça login para participar desta conversação.
Sem Objetivo
Sem utilizador atribuido
2 Participantes
A carregar...
Cancelar
Guardar
Ainda não existe conteúdo.