Fix bug related to assignees dropdown showing old values#1349
Conversation
|
Video of the fixed behaviour: |
|
@yucongkoo What's the current behaviour? Is it as follows? Suppose issue A is assigned to Adam, and issue B is assigned to Betsy. Issue B is marked as a duplicate of A -> Issue B's previous assignees (i.e., Betsy) are removed. It inherits A's assignees (i.e., Adam). Issue B is now un-marked as duplicate of A -> EDIT: |
|
@damithc Same applies to the labels. |
Got it. Yeah, that makes sense. I updated my comment to reflect this. |
|
@damithc The fix included in this PR is for the behaviour when we click on the edit assignees icon. Behaviour before the fix: Behaviour after the fix: |
Arif-Khalid
left a comment
There was a problem hiding this comment.
Great change and great PR, working as intended.
Effort is clear in investigation and effective, concise resolution of the issue.
Just a minor change required to align with Angular standards.
| this.assignees = this.issue.assignees.map((a) => a); | ||
| } | ||
|
|
||
| ngOnChanges(changes: SimpleChanges) { |
There was a problem hiding this comment.
As warned by the github actions, please inherit from the OnChanges interface

Summary:
Fixes #1348
Changes Made:
Proposed Commit Message: