Decide on how to deal with partially fixed issues #3129

Open
opened 2022-11-24 16:38:27 +00:00 by AliasAlreadyTaken · 2 comments

While the solution to add a partially fixed label is an elegant way to treat them, problems arise when we want to add them to milestones or have closure on the fixed part, while also not forgetting about the non-fixed part.

We could

  • Split the non-fixed part off into na new issue
  • Move the milestone only to the latest release
  • ???
While the solution to add a partially fixed label is an elegant way to treat them, problems arise when we want to add them to milestones or have closure on the fixed part, while also not forgetting about the non-fixed part. We could - Split the non-fixed part off into na new issue - Move the milestone only to the latest release - ???
AliasAlreadyTaken added the
1. kind/protocol
label 2022-11-24 16:38:33 +00:00
Member
  • Split the non-fixed part off into na new issue

this is probably the right way to do it, it's just a little extra work though.

> - Split the non-fixed part off into na new issue this is probably the right way to do it, it's just a little extra work though.
Author
Owner

Then let's do it like this and open a new issue when things are partially fixed. Let's still keep the partially fixed label, hinting at there must be a new issue with the remained of the grievance.

Then let's do it like this and open a new issue when things are partially fixed. Let's still keep the partially fixed label, hinting at there must be a new issue with the remained of the grievance.
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: your-land/bugtracker#3129
No description provided.