[wp-meta] [Making WordPress.org] #5118: Introduce dev-note field to Trac
Making WordPress.org
noreply at wordpress.org
Fri May 22 07:39:05 UTC 2020
#5118: Introduce dev-note field to Trac
-----------------------------+---------------------
Reporter: garrett-eclipse | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Trac | Resolution:
Keywords: has-patch |
-----------------------------+---------------------
Changes (by dd32):
* keywords: => has-patch
Comment:
PR 11 adds the field, but I'd like to get some feedback from the Core team
before deploying it.
The field doesn't show up super well in emails in my testing, it doesn't
show the proper diff as it's a Property, for example:
{{{
#11: Dev Note Testing
-----------------------------+-----------------------
Reporter: Dion Test Trac | Owner: somebody
Type: defect (bug) | Status: new
Priority: major | Milestone:
Component: component1 | Version:
Resolution: | Keywords: has-dev-note
Focuses: |
-----------------------------+-----------------------
Dev note:
This is a Dev Note.
It has multiple lines.
-----------------------------+-----------------------
Changes (by Dion Test Trac):
* dev_note: This is a Dev Note. =>
This is a Dev Note.
It has multiple lines.
}}}
On the Ticket view, it looks something like this:
{{{
* keywords: has-dev-note added
* Dev Note modified (diff)
My comment here, this is NOT the dev-note, but a comment I've added at the
same time.
}}}
But it does have a diff view, similar to what you'll see in this link I'm
going to edit in here in a moment.
I've uploaded some images of what it looks like in
https://github.com/WordPress/wordpress.org/pull/11
--
Ticket URL: <https://meta.trac.wordpress.org/ticket/5118#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org
More information about the wp-meta
mailing list