New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sort unassigned isn't working properly #3173
Comments
@rjsparks@nostrum.com changed status from |
@mark@painless-security.com commented I've just looked at this, and in the agenda editor running locally for me, the agenda editor sorting works. Could you provide steps to recreate this issue? My environment is on MacOS 10.15.7, using both Chrome 90.0.4430.85 and Safari 14.1 (15611.1.21.161.5, 15611). |
@jennifer@painless-security.com commented n.b., lflynn@amsl.com demonstrated her use of the new agenda editor and this issue was definitely still present. IIRC, this was on a freshly started agenda that had many issues in the unscheduled box. Guessing a bit, it may be either having a large number of items in the box or perhaps having issues that have not been scheduled then unscheduled. |
@jennifer@painless-security.com changed status from |
@jennifer@painless-security.com set owner to |
@jennifer@painless-security.com commented I can reproduce this now. If I create an empty agenda for, e.g., IETF-110, I can see the behavior. |
@jennifer@painless-security.com changed status from |
@jennifer@painless-security.com set resolution to |
@jennifer@painless-security.com commented Fixed in 0ade3f7: Handle groups without area when sorting unscheduled sessions in schedule editor. Fixes #3173. Commit ready for merge. |
@rjsparks@nostrum.com commented Fixed in 58c0720: Merged in 0ade3f7 from jennifer@painless-security.com: |
owner:jennifer@painless-security.com
resolution_fixed
type_defect
| by lflynn@amsl.comIn the new agenda editor, only “sort by name” works, and the other options (area, length, special requests) don’t have any effect on the order of the unassigned objects.
Issue migrated from trac:3173 at 2022-03-04 08:09:22 +0000
The text was updated successfully, but these errors were encountered: