WordPress.org

Making WordPress.org

Opened 3 months ago

Last modified 6 weeks ago

#4258 reopened enhancement

Add `needs-design-feedback` keyword to Trac

Reported by: desrosj Owned by: SergeyBiryukov
Milestone: Priority: normal
Component: Trac Keywords: has-patch
Cc:

Description

In this post on the Make WordPress Design blog, a decision made during a weekly design meeting was summarized.

The proposed change was to consolidate 3 design related keywords into 2.

  • ‘ux-feedback’ and ‘ui-feedback’ will now merge into needs-design-feedback.
  • needs-design will remain and indicate that a designer needs to create a specific design.

Attachments (1)

4258.diff (1.2 KB) - added by desrosj 3 months ago.

Download all attachments as: .zip

Change History (8)

@desrosj
3 months ago

#1 @desrosj
3 months ago

In 4258.diff:

  • Remove the ui-feedback and ux-feedback in favor of the needs-design-feedback keyword.
  • Update the description of the needs-design keyword for added clarity to its purpose.

After this change is deployed, I think that only the following report will need to be updated:

#2 @SergeyBiryukov
3 months ago

  • Owner set to SergeyBiryukov
  • Resolution set to fixed
  • Status changed from new to closed

In 8441:

Trac: Remove ui-feedback and ux-feedback keywords in favor of needs-design-feedback.

Update the description of needs-design keyword for added clarity to its purpose.

Props desrosj.
Fixes #4258.

#3 @dd32
3 months ago

  • Resolution fixed deleted
  • Status changed from closed to reopened

Re-opening for

  • ~Trac cache-buster so browsers get the new JS~ That was in [8442]
  • Trac Reports need their 'Workflow' sections updated (All reports with a Workflow section, not just UX/UI/Design reports)
  • Trac Reports might need renaming

I've Updated https://core.trac.wordpress.org/tickets/ux-feedback to

  • Also include the new keyword as a separate group from the existing tagged items (They can be bulk updated to the new keyword if someone wanted to, but
  • Changed the title to 'Needs Design Feedback'
  • The URL probably requires a systems-level change if we want that updated
  • Links to that report probably need updating in various locations.
Version 1, edited 3 months ago by dd32 (previous) (next) (diff)

#4 @desrosj
3 months ago

Thanks for following up on this, @dd32! I was waiting for the cache to bust before updating the reports.

@karmatosed and the design team plan to scrub all of the tickets with the old keywords manually to prevent having to bulk edit them.

I think displaying the tickets in a separate group on that report, for now, is great.

Eventually, we'll want a new report or a new alias for /report/35.

Let me know if I can help at all with the rest of the changes.

This ticket was mentioned in Slack in #design by karmatosed. View the logs.


3 months ago

This ticket was mentioned in Slack in #core-committers by melchoyce. View the logs.


3 months ago

This ticket was mentioned in Slack in #meta by tellyworth. View the logs.


6 weeks ago

Note: See TracTickets for help on using tickets.