[wp-meta] [Making WordPress.org] #5383: Trac: Merge "Text Changes" component with the "ui-copy" focus
Making WordPress.org
noreply at wordpress.org
Tue May 31 01:51:45 UTC 2022
#5383: Trac: Merge "Text Changes" component with the "ui-copy" focus
----------------------------+---------------------
Reporter: SergeyBiryukov | Owner: (none)
Type: task (blessed) | Status: new
Priority: normal | Milestone:
Component: Trac | Resolution:
Keywords: |
----------------------------+---------------------
Comment (by dd32):
> Rename the ui-copy focus to text-changes to clarify its purpose.
Unfortunately focuses are actually a text-field, not a category, and so
renaming is not exactly possible.
We can delete the `ui-copy` focus, and add a new `text-changes` focus, but
that won't migrate the existing tickets. Additionally, it's not possibly
to bulk-edit tickets from the Trac UI to change the focus field, without a
systems request to run a find-replace on the field.
Instead of a systems request, We might be able to add a method to our
custom Trac WP-API, which will allow running a SQL against the Trac DB to
do that find-replace.
> Remove the "Text Changes" component in favor of the focus.
I'm not sure how Trac handles deleted components for existing tickets that
are already closed on the component, I'd want to verify what happens there
first before actioning this. I suspect it's fine and it'll continue to
show the old component, just make it harder to query for them
retroactively.
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/5383#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list