You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I'm using an API connection to import requests into Jira. The reported by field is blank because the linked field does not match a user or customer in the system.
I created a custom field that's also called "reporter" in the hope that I can use Jira automation for analyst responses to be sent to the email listed in this custom field. I've tried several JSON code combinations, but with no success.
Some that I've attempted:
1)
{
"update": {
"Reporter" : [
{
"set": {
"customfield_10583": "a single line of text"
}
}
]
}
}
2)
{
"fields": {
"reporter":{"value": "{{customfield_10583}}"}
}
}
For context, the custom field is a free text field that is entered as an email address by the submitter in Wordpress that is then copied over via API.
What are the error messages you received?
Error messages + screen shot of your rule as well.
This will help on getting to the solution of your issue.
I would als rather not call the custom field reporter, as that could create a lot of confusion.
I would set it as Requester fro example.
On API doc is states the following for using a custom field on issue creation:
--data '{
"fields": {
"customfield_40000": {
"content": [
{
"content": [
{
"text": "Occurs on all orders",
"type": "text"
}
],
"type": "paragraph"
}
],
"type": "doc",
"version": 1
}
}'
Displaying both the custom and system-owned fields for demonstration purposes. I'd like the rule to overwrite the system field with the custom value. Would a good alternative be to use JSON to code the custom value as a ticket participant so that they receive customer responses?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.