You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[HOLD for payment 2023-10-09] [HOLD for payment 2023-10-05] [HOLD for payment 2023-09-27] [$1000] Stop using report.participants in favor of report.participantAccountIDs #25714
We need to stop using report.participants and instead use report.participantAccountIDs. Now that #24320 is done, we should be able to remove all uses of report.participants in the App.
Let's go through and find everywhere that we use the participants array from the Onyx report object and instead use the participantAccountIDs array instead.
changed the title [-]Stop using report.participants in favor of report.participantAccountIDs[/-][+][$1000] Stop using report.participants in favor of report.participantAccountIDs[/+]on Aug 23, 2023
changed the title [-][HOLD for payment 2023-09-27] [$1000] Stop using report.participants in favor of report.participantAccountIDs[/-][+][HOLD for payment 2023-10-05] [HOLD for payment 2023-09-27] [$1000] Stop using report.participants in favor of report.participantAccountIDs[/+]on Sep 28, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.74-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2023-10-05. 🎊
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
External issue reporter
Contributor that fixed the issue
Contributor+ that helped on the issue and/or PR
For reference, here are some details about the assignees on this issue:
changed the title [-][HOLD for payment 2023-10-05] [HOLD for payment 2023-09-27] [$1000] Stop using report.participants in favor of report.participantAccountIDs[/-][+][HOLD for payment 2023-10-09] [HOLD for payment 2023-10-05] [HOLD for payment 2023-09-27] [$1000] Stop using report.participants in favor of report.participantAccountIDs[/+]on Oct 2, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.75-12 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2023-10-09. 🎊
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
External issue reporter
Contributor that fixed the issue
Contributor+ that helped on the issue and/or PR
For reference, here are some details about the assignees on this issue:
Activity
melvin-bot commentedon Aug 22, 2023
Current assignee @puneetlath is eligible for the NewFeature assigner, not assigning anyone new.
lukemorawski commentedon Aug 23, 2023
Hey it's Lucas from Callstack. Happy to work on that ticket
[-]Stop using report.participants in favor of report.participantAccountIDs[/-][+][$1000] Stop using report.participants in favor of report.participantAccountIDs[/+]melvin-bot commentedon Aug 23, 2023
Job added to Upwork: https://www.upwork.com/jobs/~0155ce6d585250b4c1
melvin-bot commentedon Aug 23, 2023
Current assignee @puneetlath is eligible for the External assigner, not assigning anyone new.
45 remaining items
[-][HOLD for payment 2023-09-27] [$1000] Stop using report.participants in favor of report.participantAccountIDs[/-][+][HOLD for payment 2023-10-05] [HOLD for payment 2023-09-27] [$1000] Stop using report.participants in favor of report.participantAccountIDs[/+]melvin-bot commentedon Sep 28, 2023
Reviewinglabel has been removed, please complete the "BugZero Checklist".melvin-bot commentedon Sep 28, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.74-3 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2023-10-05. 🎊
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue:
puneetlath commentedon Oct 1, 2023
There are no contributors to pay out here, so I'm going to go ahead and close this.
Thanks again for your help getting this across the finish line @koko57 @burczu and @lukemorawski!
[-][HOLD for payment 2023-10-05] [HOLD for payment 2023-09-27] [$1000] Stop using report.participants in favor of report.participantAccountIDs[/-][+][HOLD for payment 2023-10-09] [HOLD for payment 2023-10-05] [HOLD for payment 2023-09-27] [$1000] Stop using report.participants in favor of report.participantAccountIDs[/+]melvin-bot commentedon Oct 2, 2023
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.3.75-12 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
If no regressions arise, payment will be issued on 2023-10-09. 🎊
After the hold period is over and BZ checklist items are completed, please complete any of the applicable payments for this issue, and check them off once done.
For reference, here are some details about the assignees on this issue:
As a reminder, here are the bonuses/penalties that should be applied for any External issue: