-
Bug
-
Resolution: Not A Defect
-
Minor
-
Jenkins - 2.38, Jira-steps plugin - 1.25
We were using jira-steps plugin version 1.2.1, where it was able to create jiraNewIssue with summary field containing int value (Build version number) assigned to a variable.
eg: 170.5.191: Build failure
But after upgrading jira-steps plugin version to 1.2.5, getting error as mentioned below.
Could you please analyse the reason?
Jira-jenkins-intgtrn #93 Console [Jenkins]
Creating new Jira issue[Pipeline] jiraNewIssueJIRA: Site - ABS Jira - Creating new issue: IssueInput(update=null, fields={project={id=10601}, summary='170.9.171': Jenkins build failure, description=Build job for package with version '170.9.171' failed., priority={name=Highest}, issuetype={id=10401}})
Error Code: 400
Error Message: {"errorMessages":[],"errors":{"summary":"Operation value must be a string"}}[Pipeline] }[Pipeline] // withEnv[Pipeline] }[Pipeline] // stage[Pipeline] }[Pipeline] // node[Pipeline] End of Pipeline[BFA] Scanning build for known causes...
[BFA] No failure causes found
[BFA] Done. 0s
ERROR: {"errorMessages":[],"errors":{"summary":"Operation value must be a string"}}Finished
: FAILURE
Regards,
Roshni