If a user resolves an issue and changes the assignee in the resolution dialog, the changelog returned by the REST API includes the status change but not the assignee change.
Is this a bug? Is there a way to know that the assignee changed?
I have just validated this using the JAVA API 7.5.0. To test, in a post-function I have a custom Script Runner script with the below text.
def map = issue.getModifiedFields()
def modifedValue = it.value
log.info(it.key + " = " + " changed from " + modifedValue.getOldValue() + " to " + modifedValue.getNewValue())
The log successfully prints for the change in assignee and resolution.
Can you please provide you code block so we can help diagnose the issue if possible?
Also let me know if you are trying to do this in a condition/validator or a post-function?
Sorry, I was referring to the REST API, not the Java API. I've updated the original question to clarify this.
This is done in a standalone C# app that we use for reporting. It is simply the response from
The returned change log includes the changes in status and resolution but not the change in assignee.
Here's what I'm talking about. In the Resolve screen, the issue's status, resolution, and assignee were all changed, but the change log returned by the REST API only has the status and resolution:
"toString": "Not a problem"
By the way, the change in assignee doesn't show in the History tab when I view the issue in Jira either. The changes to status and resolution show, but the change in assignee does not. This seems like an error.
Do you actually see the change in assignee and the change is not being logged in the history? If yes, please raise a technical support request at https://support.atlassian.com/contact/#/. The team will be able to confirm if it is a bug and help you out.
If not, we can try and investigate your workflow post-function in more detail.
Do you actually see the change in assignee and the change is not being logged in the history?
Well, what we see is that the current assignee is not the same as the last assignee shown in the history, so at some point there was a reassignment that is not in the history (or the change log).
I suspect that this happens when a case is automatically reassigned during resolution, which occurs because we have "Assign the issue to the reporter" as a Post function. I think that this action doesn't go into the history, even though (IMO) it really should.
I will contact tech support.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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