it is decently important to handle them asap when they arrive so that we can avoid building up too much backlog.

Discovery should focus on trust boundaries, authentication flows, parsers, shared services, and legacy code that still sits on critical paths.

it's about concentration prioritization and drifting away and doing something different

But soon we began to ask ourselves some very important questions:Who decides what products we should build? How do they decide?How do they know that what we build will be useful?

Eager-merging since this is a bug on prod. Happy to rework this solution as needed if another approach is preferable.

Here are some questions that will help you to figure it out: Which goal do I think about the most? Which goal can give me the most energy? Is this in line with my true values? Which goals do not depend on other people or circumstances? Which goals give me a heavy sensation when I think about them? Which goals give me positive feelings when I think of them? In ten years from now, how important will the goal be to me? What achievements would make me feel proud of myself? Which goals fit best within my current life context?

I fail to understand how this is such a low priority. Code review is one of the most basic and critical portions of development lifecycle, and prior to discovery of this ticket I literally had to roll an entire other repository manager just to perform that correctly when I discovered entire directories of changes had been omitted from the Gitlab generated MR. We actually found that in order to get the change set fix to apply reliably, that it is required to add "?w=1" to the url even after updating the white space setting.

I got stuck with tests here #443 and I need to switch to other more prioritised work. Maybe somebody will take over when time allows.

This hasn't yet been scheduled, but we're tracking it on our backlog as something we want to do this year. A few months ago, we arranged for additional capacity to address items like this that have waited for so long. Now that additional capacity is available, it's just a matter of scheduling based on relative priority. We're anxious to get this one done, and I hope to soon have a clearer date to post here.

Whenever I get a new cookbook, I go through it and bookmark recipes that are either worth considering, or that go on a list to definitely try. Usually the maybes outnumber the definites. In this case, I've bookmarked a large number of recipes that I DEFINITELY will make.

Requirements Triage or prioritization of requirements is another activity which often follows analysis.

GTD strategies

put it in our %Backlog (meaning GitLab, Inc. currently doesn't prioritize it over other items that are scheduled

It does not fit entirely in our ~"Product Vision 2019" for this year to prioritize this issue over others that we have focused on

Priority labels

Leads and product managers handle most of the scheduling into milestones.

Product Prioritize development

Prioritization is a collaboration between Product, UX, Data, and Engineering. To help our group prioritize issues within a milestone, we utilize the milestone priority labels:

Some conventions reverse the order of priorities, considering lower values to be higher priority