jneth8
New Contributor
Joined 7 years ago
User Profile
User Widgets
Contributions
ReadyAPI - Jira Integration
I am attempting to use the Jira plugin and have it setup. I have the connections configured and they are working. However, when trying to create a new Jira item, the screen displayed does not have all the needed information. Looking at the wiki for the plugin, the screen shots for creating a new Jira item have a lot more information than I am seeing. The connection to Jira is fine as I am able to click the Jira icon from a test case and select my project. It also is retrieving the issue types correctly from Jira. However, when filling out the Summary, which is the only required field displayed to me, the creation of the item fails because it is missing more required information. Jira version = 9.12.15 ReadyAPI Version = 3.58.0 Jira plugin version = 1.6.7 There are no errors in the error log. The only "error" I see is in the HTTP log after the creation of the Jira item fails: RestClientException{statusCode=Optional.of(400), errorCollections=[ErrorCollection{status=400, errors={customfield_10010=Acceptance Criteria is required., customfield_11200=Category is required.}, errorMessages=[]}]} In the ReadyAPI log, I see some records like this. It seems to be getting all the fields from Jira, but even after it checks for it, it still just displays the issue type. For example, there are the lines where it appears to find the "description" field. Attached a screen shot of the "Create Story" screen. Any help or guidance would be appreciated. Tue Feb 25 12:47:33 CST 2025: INFO: getFieldInfo.bugTrackerProvider : com.smartbear.ready.plugin.jira.impl.JiraProvider@4a9b76c, selectedProject : EWS, fieldInfoKey: description Tue Feb 25 12:47:33 CST 2025: INFO: [JiraProvider].[getProjectFieldsInternal] we reach here Tue Feb 25 12:47:33 CST 2025: INFO: getFieldInfo.bugTrackerProvider : com.smartbear.ready.plugin.jira.impl.JiraProvider@4a9b76c, selectedProject : EWS, fieldInfoKey: description Tue Feb 25 12:47:33 CST 2025: INFO: [JiraProvider].[getProjectFieldsInternal] we reach here Tue Feb 25 12:47:48 CST 2025: INFO: [CreateIssueMetadataJsonParserExt].[parse] json: {"maxResults":50,"startAt":0,"total":16,"isLast":true,"values":[{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/1","id":"1","description":"A problem which impairs or prevents the functions of the product.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13803&avatarType=issuetype","name":"Bug","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10100","id":"10100","description":"Spikes are a type of story used for activities such as research, design, exploration, or prototyping. They are used to gain knowledge in order to reduce risk.","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/exclamation.png","name":"Spike","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10300","id":"10300","description":"This subtask represents a defect found during testing or review of a Story","iconUrl":"https:\/\/jira\/images\/icons\/subtask-defect.png","name":"Defect","subtask":true},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10400","id":"10400","description":"An impediment is anything that is slowing or stopping the team(s) or effort down.","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/delete.png","name":"Impediment","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10700","id":"10700","description":"An announcement of information that is not an impediment or risk.","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/blank.png","name":"Notification","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10701","id":"10701","description":"Any uncertain event that can have an impact on the success.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13803&avatarType=issuetype","name":"Risk","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10702","id":"10702","description":"Use for technical analysis, research work done by team member for detail design type work. ","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/defect.png","name":"Technical Analysis","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10703","id":"10703","description":"Use for solution analysis, work done by team member for defining and clarifying discovery efforts, requirements, MBI\/MTI and features. Mainly used by solution analysts.","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/defect.png","name":"Solution Analysis","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10804","id":"10804","description":"This is an \"initial placeholder\" issue and optional to use. It generally only includes the summary and possibly a supporting sentence or two","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=14404&avatarType=issuetype","name":"Raw","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/3","id":"3","description":"A task that needs to be done.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13818&avatarType=issuetype","name":"Task","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/4","id":"4","description":"An improvement or enhancement to an existing feature or task.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13810&avatarType=issuetype","name":"Improvement","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/5","id":"5","description":"The sub-task of the issue","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13816&avatarType=issuetype","name":"Sub-task","subtask":true},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/6","id":"6","description":"Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=15719&avatarType=issuetype","name":"Feature","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/7","id":"7","description":"Created by Jira Software - do not edit or delete. Issue type for a user story.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13815&avatarType=issuetype","name":"Story","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/8","id":"8","description":"Created by GreenHopper - do not edit or delete. Issue type for a technical task.","iconUrl":"https:\/\/jira\/images\/icons\/ico_task.png","name":"Technical task","subtask":true},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/9","id":"9","description":"Unit, Behavior, or Test Case","iconUrl":"https:\/\/jira\/images\/icons\/chem.png","name":"Test task","subtask":true}]} Tue Feb 25 12:47:48 CST 2025: INFO: [CreateIssueMetadataJsonParserExt].[parse] json: {"maxResults":50,"startAt":0,"total":16,"isLast":true,"values":[{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/1","id":"1","description":"A problem which impairs or prevents the functions of the product.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13803&avatarType=issuetype","name":"Bug","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10100","id":"10100","description":"Spikes are a type of story used for activities such as research, design, exploration, or prototyping. They are used to gain knowledge in order to reduce risk.","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/exclamation.png","name":"Spike","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10300","id":"10300","description":"This subtask represents a defect found during testing or review of a Story","iconUrl":"https:\/\/jira\/images\/icons\/subtask-defect.png","name":"Defect","subtask":true},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10400","id":"10400","description":"An impediment is anything that is slowing or stopping the team(s) or effort down.","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/delete.png","name":"Impediment","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10700","id":"10700","description":"An announcement of information that is not an impediment or risk.","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/blank.png","name":"Notification","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10701","id":"10701","description":"Any uncertain event that can have an impact on the success.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13803&avatarType=issuetype","name":"Risk","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10702","id":"10702","description":"Use for technical analysis, research work done by team member for detail design type work. ","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/defect.png","name":"Technical Analysis","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10703","id":"10703","description":"Use for solution analysis, work done by team member for defining and clarifying discovery efforts, requirements, MBI\/MTI and features. Mainly used by solution analysts.","iconUrl":"https:\/\/jira\/images\/icons\/issuetypes\/defect.png","name":"Solution Analysis","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/10804","id":"10804","description":"This is an \"initial placeholder\" issue and optional to use. It generally only includes the summary and possibly a supporting sentence or two","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=14404&avatarType=issuetype","name":"Raw","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/3","id":"3","description":"A task that needs to be done.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13818&avatarType=issuetype","name":"Task","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/4","id":"4","description":"An improvement or enhancement to an existing feature or task.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13810&avatarType=issuetype","name":"Improvement","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/5","id":"5","description":"The sub-task of the issue","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13816&avatarType=issuetype","name":"Sub-task","subtask":true},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/6","id":"6","description":"Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=15719&avatarType=issuetype","name":"Feature","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/7","id":"7","description":"Created by Jira Software - do not edit or delete. Issue type for a user story.","iconUrl":"https:\/\/jira\/secure\/viewavatar?size=xsmall&avatarId=13815&avatarType=issuetype","name":"Story","subtask":false},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/8","id":"8","description":"Created by GreenHopper - do not edit or delete. Issue type for a technical task.","iconUrl":"https:\/\/jira\/images\/icons\/ico_task.png","name":"Technical task","subtask":true},{"self":"https:\/\/jira\/rest\/api\/2\/issuetype\/9","id":"9","description":"Unit, Behavior, or Test Case","iconUrl":"https:\/\/jira\/images\/icons\/chem.png","name":"Test task","subtask":true}]}76Views0likes0CommentsRe: How do I pass a test case while ignoring only certain failed test steps?
I know it is not possible out of the box. As mentioned, I already have a groovy script to retry the REST step in case of a failure. What I want is to ignore the initial failure of that REST step at the test case level and have the test case pass if all other steps outside this one particular test step pass. Is there a way to manipulate the log files so that the test case thinks the test step passed?3.3KViews0likes1CommentHow do I pass a test case while ignoring only certain failed test steps?
I have a test case that has multiple test steps. Two of them are calling a REST endpoint that was not developed by my organization. It's essentially an API for viewing a log. However, sometimes when calling the API, it fails. No payload is returned, no HTTP status is returned, it is a null payload. I have accounted for this by not putting any assertions on the test step and I have a groovy test step right after to evaluate the payload. If the payload is null, I return to the to REST call and run it again. Once it returns a payload, the groovy script will allow the test case to move to the next step. When the test case completes, if one of the API calls failed the entire test case is failed even though it eventually passed. It seems that the test case is looking at the log and if any test step failed at any point, the test case failed. How can ignore the failures only for those specific REST calls? If any other test step fails, I still want to the test case to fail. I have attempted to add a script to disable the "Fail TestCase if it has failed TestSteps" option before the REST steps and then re-enable it after they have run, but the test case still fails. Thank you in advance for any help.Solved3.6KViews0likes6Comments