Change Details

== Preamble == If you visit the page `/feed/` you see some basic filters: > {F30702, size=full} These filters are useful to discover or remember what was done on a certain day and tell others (your boss? your customers?) what you have done in a specific day or period. It also helps in filling "intervention reports" - something very common in any company where every employee have to enter into a legacy management system how they invested their working hours (e.g. this monday I've probably spent 2 hours on this task, etc.). == Problem == It's difficult to answer the question "Hey Valerio, what you have done today?". You very probably would like to tell something like this: - `T123: Fix production` - I've created the task - I've added details in the description - I've attached some commits - I've resolved in the same day - `T124: Buy chocolate to my boss` - I've created the task - I've updated the descriptions 100000 times - It's still opened So as you can see, in natural languages, it's useful to "group actions by object" but at the moment this feature is not available. == Workaround == A known workaround is to run this "group by" in your mind, on the fly, only thanks to your powerful imagination. Or, create something with Conduit APIs. == Proposed solution == In the `/feed/` advanced search, add a checkbox: * [ ] Hide minor activities When checked, as default it should hide these activities: * move a Task from a workboard to another * change Task priority * add/remove a Tag from something * subscribe/unsubscribe * updated the name of * award a token * change policy * set the point value * placed ... up from grabs * //what else?// In this way, other kind of activities which in a major way describe the hours spent by a worker - such as comments, commits, Task creation, Task marked as Resolved etc. can take __more__ visibility, speeding up intervention report operations. NOTE: Telling "what is minor" can be very subjective, but we you can rely on common sense when saying that stuff like "subcribe" certainly always carries a lot less weight than "doing a commit". That's the spirit of this filter. We can provide a default and then allow customization via code or other ways to be discussed later.

== Preamble == If you visit the page `/feed/` you see some basic filters: > {F30702, size=full} These filters are useful to discover or remember what was done on a certain day and tell others (your boss? your customers?) what you have done in a specific day or period. It also helps in filling "intervention reports" - something very common in any company where every employee have to enter into a legacy management system how they invested their working hours (e.g. this monday I've probably spent 2 hours on this task, etc.). == Problem == It's difficult to answer the question "Hey Valerio, what you have done today?". You very probably would like to tell something like this: - `T123: Fix production` - I've created the task - I've added details in the description - I've attached some commits - I've resolved in the same day - `T124: Buy chocolate to my boss` - I've created the task - I've updated the descriptions 100000 times - It's still opened So as you can see, in natural languages, it's useful to "group actions by object" but at the moment this feature is not available. == Workaround == A known workaround is to run this "group by" in your mind, on the fly, only thanks to your powerful imagination. Or, create something with Conduit APIs. == Proposed solution == In the `/feed/` advanced search, add a select box: * [ ] Buck By <None | Object> When checked, transactions happening in a specific object will be "bucked" (grouped) by that object. A bit like Differential revisions are bucked by action.

== Preamble == If you visit the page `/feed/` you see some basic filters: > {F30702, size=full} These filters are useful to discover or remember what was done on a certain day and tell others (your boss? your customers?) what you have done in a specific day or period. It also helps in filling "intervention reports" - something very common in any company where every employee have to enter into a legacy management system how they invested their working hours (e.g. this monday I've probably spent 2 hours on this task, etc.). == Problem == It's difficult to answer the question "Hey Valerio, what you have done today?". You very probably would like to tell something like this: - `T123: Fix production` - I've created the task - I've added details in the description - I've attached some commits - I've resolved in the same day - `T124: Buy chocolate to my boss` - I've created the task - I've updated the descriptions 100000 times - It's still opened So as you can see, in natural languages, it's useful to "group actions by object" but at the moment this feature is not available. == Workaround == A known workaround is to run this "group by" in your mind, on the fly, only thanks to your powerful imagination. Or, create something with Conduit APIs. == Proposed solution == In the `/feed/` advanced search, add a checkselect box: * [ ] Hide minor activitiesBuck By <None | Object> When checked, as default it should hide these activities: * move a Task from a workboard to another * change Task priority * add/remove a Tag from something * subscribe/unsubscribe * updated the name of * award a token * change policy * set the point value * placed ... up from grabs * //what else?// In this way, other kind of activities which in a major way describe the hours spent by a worker - such as comments, commits, Task creation, Task marked as Resolved etc. can take __more__ visibility, speeding up intervention report operations. NOTE: Telling "what is minor" can be very subjective, but we you can rely on common sense when saying that stuff like "subcribe" certainly always carries a lot less weight than "doing a commit". That's the spirit of this filtertransactions happening in a specific object will be "bucked" (grouped) by that object. We can provide a default and then allow customization via code or other ways to be discussed laterA bit like Differential revisions are bucked by action.