nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Getting 'Reporter field is required' error when creating Jira issue from service now via REST call

Kanhaiya Panigrahi

I am creating jira issue from Service now via REST call which was working until yesterday

Suddenly i am getting 'Reporter' is mandatory error.

The user is having permission to modify the Reported for field and create jira issue.

When I make 'reporter' an option field, it is working. But when it is Required, It is not working.

Can anyone provide solution for this?

Accepted answers

DPKJ

@Kanhaiya Panigrahi if a field is required you need to pass some value to it, otherwise API will surely give error.

All comments

DPKJ

@Kanhaiya Panigrahi if a field is required you need to pass some value to it, otherwise API will surely give error.

Kanhaiya Panigrahi

@DPKJ I am passing the username.

Kanhaiya Panigrahi

@DPKJ

{
"fields":{
"issuetype":{
"name":"Bug"
},
"project":{
"key":"SNOW"
},
"summary":"Issue with creating Jira tickets from ITWorx",
"description":" Issue with creating Jira tickets from ITWorx",
"priority":{
"name":"Low"
},
"customfield_10400":"INC0348345",
"customfield_10401":"https://ptc.service-now.com/incident.do?sys_id=1868e1251343cc100a083ff18144b0d9",
"reporter":{
"name":"Jira User"
}
}
}

Kanhaiya Panigrahi

And until yesterday it was working but suddenly it stopped.

I tried with id, name and email too for the reporter but its not working.

Marcin_Kujawa

I have the same problem. Reporter field has value (username), but I receive 'Repoter is required' exception.

Marcin_Kujawa

I set Reporter as an optional field and it worked, but it's just workaround, not solution.

Kanhaiya Panigrahi

@Marcin_Kujawa Thanks for the solution. I have already tried this yesterday and yes it is just a workaround not a permanent solution.

If you find anything permanent solution please post it here too.

Meanwhile I am also investigating & if i get it then will post.

Kanhaiya Panigrahi

@Marcin_Kujawa You can pass the userid, just open the user's profile in JIRA & pick it from the URL.

{
"fields":{
"issuetype":{
"name":"Bug"
},
"project":{
"key":"SNOW"
},
"summary":"Issue with creating Jira tickets from ITWorx2",
"description":" Issue with creating Jira tickets from ITWorx2",
"priority":{
"name":"Low"
},
"customfield_10400":"INC0348345",
"customfield_10401":"https://ptc.service-now.com/incident.do?sys_id=1868e1251343cc100a083ff18144b0d9",
"reporter":{
"id":"59f6fdf0883e38789b8e1e8f"
}
}
}

Tom Boyle

We've had the same issue this week ourselves. We've currently also worked around it by hardcoding an ID but defeats the point of the field.

It has been working for months up until now.

Has something changed in Jira in relation to the Reporter field?

DPKJ

@Tom Boyle Yes, GDPR has started kicking in for API's. So using ID field of user is best bet at this time.

Kim Kokholm

Hi
i have similar issues though just in Powershell

Script

$parameters = @{
Project = 'INF'
#customfield_10930 = 'INF-2312'
issueType = 'Task'
Reporter ='kim.kokholm'
Summary = 'Test issue from PowerShell'
Description = "This is a sample issue created by ." }

New-JiraIssue @parameters

error

Invoke-JiraMethod :
reporter
--------
Reporter is required.
At C:\Program Files\WindowsPowerShell\Modules\JiraPS\2.12.5\JiraPS.psm1:3842 char:27
+ if ($result = Invoke-JiraMethod @parameter) {
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidResult: (:) [Invoke-JiraMethod], RuntimeException
+ FullyQualifiedErrorId : InvalidResponse.Status400,Invoke-JiraMethod

Francisco Mancardi

Why the hell they have did this change!!!, this has broken my integration, and is IMHO a very bad option when you need to integrate different systems.

jyparida

how can we user name instead of id to set reporter field is there nay way

Brian McGrath

has anyone figured out 'reporter is required' for PowerShell? I am having same issue. thanks!

Guillermo Robaudo

Hi @Brian McGrath it work for me
I were introduced reporter inside Fields with my customefields as you can see below and get Account ID beforehands from email address

$user = "email@domain.com"
$reporter = (Get-JiraConfigServer -ErrorAction Stop) + "/rest/api/3/user/search?query=" + $user
$accountId = (Invoke-JiraMethod $reporter).accountId # you need to use ID due GDPR

$parameters = @{
Project = "PROJECTNAME"
IssueType = "ISSUETYPE"
Summary = "Test issue from PowerShell XXX"

Fields = @{
customfield_11449 = { value = "option3" }
reporter = @{ "id" = $accountId }

}
}
New-JiraIssue @parameters

References

Solved: How to do user search with v3 REST API? (atlassian.com)

Custom Fields - Docs | AtlassianPS

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud