Opened 11 years ago
Last modified 3 years ago
#291 new enhancement
Bring core trac improvements to other trac instances (meta, bbPress, BuddyPress)
Reported by: | siobhan | Owned by: | |
---|---|---|---|
Milestone: | Priority: | high | |
Component: | Trac | Keywords: | |
Cc: |
Description
Nacin has introduced some lovely changes to core trac. It would be fantastic to have the same functionality on meta trac. I'm particularly thinking about the ability to star and follow tickets, but also the duplicate ticket suggestions and the nice box that mentions that someone is opening their first ticket.
In relation to this - the CC functionality seems to have disappeared on meta trac, but it hasn't been replaced by the follow functionality so there's currently no way to follow a ticket.
Change History (34)
#4
@
11 years ago
That all sounds great. I was mostly after the CC functionality - if you could bring that back that would be awesome for now.
#5
follow-up:
↓ 9
@
11 years ago
Brought CC back. No idea where it went, but it's here now.
General FYI, almost every other new piece of functionality was brought to other Tracs: http://make.wordpress.org/meta/2014/01/15/trac-updates/.
This ticket was mentioned in Slack in #meta by netweb. View the logs.
10 years ago
#9
in reply to:
↑ 5
@
10 years ago
Replying to nacin:
Brought CC back. No idea where it went, but it's here now.
General FYI, almost every other new piece of functionality was brought to other Tracs: http://make.wordpress.org/meta/2014/01/15/trac-updates/.
It's gone again :/
This ticket was mentioned in Slack in #meta by sam. View the logs.
9 years ago
This ticket was mentioned in Slack in #core-flow by sam. View the logs.
9 years ago
#16
follow-up:
↓ 18
@
9 years ago
Okay, this is basically done. Now it's just stuff around the edges:
- Reports that let you see your favorites, etc.
- Number of stars as a report column (if necessary)
- Does meta.trac need/want https://make.wordpress.org/core/components/?
cc @sam
#17
@
9 years ago
Note I plan to do this for additional Tracs too, now that a conversion to MySQL is no longer required.
#18
in reply to:
↑ 16
@
9 years ago
Replying to nacin:
- Does meta.trac need/want https://make.wordpress.org/core/components/?
Meh.
We kind of have them (see our team page), but I don't think we need something that formal.
This ticket was mentioned in Slack in #buddypress by netweb. View the logs.
9 years ago
#20
in reply to:
↑ 3
@
9 years ago
Replying to nacin:
Notifications will be ported to meta/bbpress/buddypress tracs soon, we're just trying to make sure the MySQL server we set up for core trac can support it under its current config. With that comes the newbie notices.
Duplicate ticket suggestions are separate. They're not difficult to add elsewhere, but they are pretty low quality at the moment.
I have *no* idea where CC went. Will try to bring that back for the moment.
CC functionality has vanished from both bbPress and BuddyPress tracs ¯\_(ツ)_/¯
@nacin Is there much left to do to bring these changes to the bb's?
#21
@
8 years ago
- Priority changed from normal to high
- Summary changed from Bring core trac changes to meta trac to Bring core trac improvements to other trac instances (meta, bbPress, BuddyPress)
This ticket was mentioned in Slack in #buddypress by netweb. View the logs.
8 years ago
This ticket was mentioned in Slack in #buddypress by netweb. View the logs.
8 years ago
This ticket was mentioned in Slack in #buddypress by netweb. View the logs.
8 years ago
This ticket was mentioned in Slack in #polyglots-events by netweb. View the logs.
7 years ago
This ticket was mentioned in Slack in #buddypress by netweb. View the logs.
7 years ago
This ticket was mentioned in Slack in #meta by netweb. View the logs.
7 years ago
This ticket was mentioned in Slack in #accessibility by sergey. View the logs.
3 years ago
#29
@
3 years ago
This came up in a recent Accessibility Team meeting.
There is currently no Focus field on Meta Trac, which makes it harder to mark accessibility-related tickets as such, and to search for them later.
On Core Trac, you can use a query like this:
https://core.trac.wordpress.org/query?status=!closed&focuses=~accessibility&order=priority
On Meta Trac, the only (not very reliable) way is to search for "accessibility" in the ticket summary and description:
https://meta.trac.wordpress.org/query?status=!closed&summary=~accessibility&or&status=!closed&description=~accessibility&order=priority
#30
@
3 years ago
Things from above:
- Bring Focuses to all Trac's
- CCs (I'm pretty sure this was intentional to remove)
Other things that would be nice to standardise:
- BlackMagic disabling the Milestone/Priority fields for non-privileged users (On for Core, supposed to exist on BuddyPress but extension isn't enabled)
- GitHub PRs for bbPress/Buddypress (on for Core/Meta)
This ticket was mentioned in Slack in #bbpress by dd32. View the logs.
3 years ago
#32
@
3 years ago
It would also be nice to have a consistent header across Trac instances. Currently, the location and appearance of "Timeline", "New Ticket", "Browse Source" links is quite different between Core Trac and Meta Trac.
Notifications will be ported to meta/bbpress/buddypress tracs soon, we're just trying to make sure the MySQL server we set up for core trac can support it under its current config. With that comes the newbie notices.
Duplicate ticket suggestions are separate. They're not difficult to add elsewhere, but they are pretty low quality at the moment.
I have *no* idea where CC went. Will try to bring that back for the moment.