[ https://issues.jboss.org/browse/JBIDE-24112?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24112: ------------------------------------ [~jeffmaury] As curently set up, jiralint machine user can create but cannot assign issues to component leads. So the new job I created simply creates an email, sends it to you, and you can then run the instructions to fetch the jbosstools-build-ci project, and run the createnewandnoteworth.py script with the correct settings passed to it, including YOUR username/password. Since it's run as YOU and you have assignment rights, the issues are created and assigned to the component leads automatically. (Issue assignment was added in JBIDE-23536 some time ago, per your request.) This is the same setup for when it's time to update root poms and create branches -- generate an email with instructions, which you then run using your username/password for issues.jboss.org. If we create NEW machine user which has assignment rights, we could further simplify this so that the bash/python scripts could be run from Jenkins via the new machine user, and there'd be no need to generate emails w/ instructions. We have a machine user in github called *devstudio-release* used in Jenkins to push commits to the github repos that back up download.jboss.org and devstudio.redhat.com. I could create a similar one in issues.jboss.org that would then be granted create & assignment rights for JBDS and JBIDE projects. [~maxandersen] thanks for the clarification. [~jeffmaury] should we create a new machine user? -- This message was sent by Atlassian JIRA (v7.2.3#72005)