Review new way to encode - report weekly tasks

[cmoulliard]

@Team

Can you please review this page and tell me what you think about the process to be used for the team members to encode their daily tasks : https://github.com/snowdrop/snowdrop-team/blob/master/README.md ?

The point that I still dont know is : Is it better to have one issue / week containing a list of tasks (see my Week 19 : Tasks issue) or to create x issues / week but then how could we group or find them easily ?

Here is my board example https://github.com/snowdrop/snowdrop-team#workspaces/weekly-report-5ea91ba086ff1a94621193a6/board?authors=cmoulliard&filterLogic=any&repos=259889605

@aureamunoz @gytis @geoand @jacobdotcosta @iocanel @metacosm

[geoand]

It's certainly simpler to have one issue.
What would the benefit of having multiple issues be?

[metacosm]

One thing I don't understand is why we need a task per week? Is it for tracking purpose?
My view on how it should work: one epic per week if that is need, everything else is tickets assigned to that epic.
Why? For several reasons:

• Having a task per week is work that doesn't (seemingly) add any value
• You will need to edit the checklist multiple times and not really be able to track progress / comment on each task
• You cannot manipulate the check list as easily as you could with issues on the board (you cannot re-assign the task and track that re-assignment, you cannot start/stop progress, mark it as done automatically)
• We're using an issue tracker, so let's really use it instead of encoding information in text files that are not trackable.

[metacosm]

I also don't like the fact that right now everyone is spammed with what happens in this project: this adds a lot of noise with little value. This is the same issue I had with snowdrop-project previously which was used as a bucket to put issues which would have better be suited being filed elsewhere…

[cmoulliard]

One thing I don't understand is why we need a task per week? Is it for tracking purpose?

This is still under investigation till we know if the tracking reporting tool can collect issues per user and falling within the range From Thursday to Thursday Next Week. If that works, then it is not needed to have an issue = week tasks.

[cmoulliard]

• You will need to edit the checklist multiple times and not really be able to track progress / comment on each task

I have also the same concern too ;-) like also that we cannot see them within the Zenhub workspace. This is also an issue that we have too using Trello

[cmoulliard]

• You cannot manipulate the check list as easily as you could with issues on the board (you cannot re-assign the task and track that re-assignment, you cannot start/stop progress, mark it as done automatically)

+1

[metacosm]

• You cannot manipulate the check list as easily as you could with issues on the board (you cannot re-assign the task and track that re-assignment, you cannot start/stop progress, mark it as done automatically)

+1

Not to mention that you could easily remove task from the checklist without being able to track that 😸