Problem
DEV-360 requires every draft PR to link a Problem issue, even when the PR
itself already makes the work visible and traceable, which is the exact goal
DEV-360 states as its reason for existing. When the work is opened as a PR
directly, filing a separate Problem first adds a step that duplicates what the
PR already shows, instead of tracking anything that was actually blocked.
Solution
Once this merges, contributors can open a draft PR straight from a Goal or a
review comment without first filing a separate Problem issue, when the PR
alone already makes the work visible and traceable. Amend DEV-360 so a Problem
is preferred but not required once a draft PR exists for the work, and keep
DEV-160 for work that needs Goal-level stakeholder visibility before any PR
exists.
Problem
DEV-360 requires every draft PR to link a Problem issue, even when the PR
itself already makes the work visible and traceable, which is the exact goal
DEV-360 states as its reason for existing. When the work is opened as a PR
directly, filing a separate Problem first adds a step that duplicates what the
PR already shows, instead of tracking anything that was actually blocked.
Solution
Once this merges, contributors can open a draft PR straight from a Goal or a
review comment without first filing a separate Problem issue, when the PR
alone already makes the work visible and traceable. Amend DEV-360 so a Problem
is preferred but not required once a draft PR exists for the work, and keep
DEV-160 for work that needs Goal-level stakeholder visibility before any PR
exists.