Improve REST handling of txn CFs #183
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
please merge this |
|
Had to nuke the mason cache after watching my 4.4.2 install but seems to work perfectly. |
|
This is a duplicate of my PR #178. Naturally I'd like either this one, or that one to be merged. ;) |
|
Seems like an obvious feature to pull in. Not sure why its delayed. |
added 6 commits
August 17, 2017 12:10
This causes a warning to be thrown if you send comments via REST without these fields being set.
Allow tests to easily create or reuse transaction custom fields on a queue.
puck
force-pushed
the
4.2/add-txn-rest-customfield
branch
from
d04f1d8 to
94be184
Compare
|
Looks like my rebasing has confused this PR. Probably better to grab #178 . |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
http://lists.bestpractical.com/pipermail/rt-devel/2016-March/012530.html