I am currently working on a small plugin that allows us to migrate from an old legacy issue tracker to Jira. In this the workflow should be that all legacy issues are mapped to components of a Jira project and are automatically assigned to the project-lead of the corresponding component. This had worked in Jira 5.x but now I'm working on 6.x. The components are setup to have a component lead and are configured to automatically assign issues to the component lead. When creating issues using the Web UI this works fine. Unfortunately when creating issues programatically using the IssueService.validateCreate I get errors:
[jira.issue.fields.AssigneeSystemField] Validation error: Issues must be assigned
Do I have to do something differently in 6.1-20130626?
Chris
Community moderators have prevented the ability to post new answers.
My current solution is to get the component, lookup the component lead and manually set this, but this is not quite the same. For example if the configuration for the component was changed to automatically assign to someone else, this wouldn't be respected by the plugin. It's a working workaround, but it's not quite the solution I was looking for.
I'm having the same issue in JIRA v6.4.8.
I create an issue specifying a component, issue is NOT assigned to component lead. Strange. And quite annoying
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well as noone seems to be able to help and the "Open question reminder" Emails are starting to become anoying, I'll closequestion. this
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.