I'm setting assignee in a script runner post function via
issueService.assign(user, assignResult) ....
I see this assignee in the issue. But in the issue navigator it still shows unassigned.
If I update the issue (f.e. update the description) or reindex the issue manually , the assignee is also show in the issue navigator.
Extra funny: I'm using the script in 2 projects. In first project I don't have the update problem.
I've also tried to reindex in the post function => no effect for the 2 nd project.
boolean wasIndexing = ImportUtils.isIndexIssues(); IssueManager issueManager = ComponentAccessor.getIssueManager(); ComponentAccessor.getIssueIndexManager().reIndex(executionResult.getIssue()); ImportUtils.setIndexIssues(wasIndexing);
What could be the reason. Bug in JIRA or ???
What could the issueService.assign() forget ot trigger ?
Yes the workflow is similar and should be ok. Post function is before index in worfklow => should be ok. But I found out the diferrence between the other project. The working project has an additional StateListener (Scriptrunner) setting some date values. So the issue is updated again => and this "solves" the update for the assignee (lucky strike). So the real problem is that the issueService.assing() has some refesh problem ??? Any idea therefore?
It started as any story starts, on a normal, rainy day. Admin meets App, and her name was Klok2, and like any first relationship we were both trying to make it work but neither one knew what...
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