I am facing a weird problem with JIRA Java API. Below is the snippet code.
I make a transition which changes issue's status from WAITING FOR SUPPORT to RESOLVED with resolution DONE.
IssueInputParameters issueInputParameters = issueService.newIssueInputParameters(); issueInputParameters.setRetainExistingValuesWhenParameterNotProvided(true, true); issueInputParameters.setResolutionId(resolutionId); IssueService.TransitionValidationResult transitionResult = issueService.validateTransition(user, issue.getId(), action.getId(), issueInputParameters); IssueResult result = issueService.transition(user, transitionResult); //result.isValid == true
However, as seen in the screenshot below there is a successful changelog regarding the status change but Issue's Status does not. Issue's status is WAITING FOR SUPPORT, but changelog says that it should have changed to RESOLVED.
This code was working well before.
Thanks in advance for any help.
Transition is triggered by another issue's transition.
There are two issues. One is Service Desk issue and another one is an issue of any project which is linked Service Desk issue. When linked issue is resolved, I want to have the Service Desk issue resolved too by programmatically.
(PS: I can not resolve Service Desk issue with Automation because I want to wait for all linked issues to be resolved. And when last linked issues is resolved, main Service Desk isssue needs to be resolved. )
Sorry for the lack of information.
To answer “How scrum works,” most of the teams I've worked with first addressed the question: “where to start?” That question applies to both implementation and improvements on the Scrum framew...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs