-
Bug
-
Resolution: Obsolete
-
Medium (View bug fix roadmap)
-
3.13.1
-
3.13
-
The Custom Assignee Resolver plugin as described on cac no longer works.
The cause is that Issue Views Plugin requires the Field Manager. The Field Manager gets injected with the Assignee System Field which in turn is injected with the Assignee Resolver.
This means that if the Issue Views Plugin is loaded before the Custom Assignee Resolver plugin, the Field Manager is instantiated with the Default Assignee Resolver, and not the Custom. Issue creation uses the fields on the Field Manager to create the values, and therefore uses the Default Assignee Resolver instead of the custom.
Hello,
This issue has been closed as we do not believe that it is present in the latest version of JIRA.
If you are able to reproduce this issue in the latest version of JIRA, please let us know via a new bug report in this site (https://jira.atlassian.com/).
Please make sure you include reproduction steps, affected jira versions and browser versions(if applicable), so that our team is able to verify any new bug report.
Thanks,
Ben Magro - JIRA Service Enablement