# Create jira issue in ansible

**URL:** <https://forum.ansible.com/t/create-jira-issue-in-ansible/22007>\
**Category:** Ansible Project\
**Created:** [July 13, 2016, 12:14pm UTC](https://forum.ansible.com/t/create-jira-issue-in-ansible/22007 "2016-07-13T12:14:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ivo\_Hechmann](https://avatars.discourse-cdn.com/v4/letter/i/91b2a8/32.png) [@Ivo\_Hechmann](https://forum.ansible.com/u/Ivo_Hechmann)\
**Post date:** [July 13, 2016, 12:14pm UTC](https://forum.ansible.com/t/create-jira-issue-in-ansible/22007/1 "2016-07-13T12:14:08Z")

</div>

Hello Team ansible.

Since upgrade to 2.1.0.0, I cannot use the jira module anymore.

Error message is “fatal: [hostname]: FAILED! =\> {“changed”: false, “failed”: true, “msg”: “dictionary update sequence element #0 has length 1; 2 is required”}”

The playbook Looks like

- hosts: xxxx

tasks:

- name: (JIRA) Sample ansible issue  
jira: description=something issuetype=Bug operation=create password=XXXX project=xxx summary=test uri=[https://hostname.com](https://hostname.com) username=XXX

Output in ansible 2.1.0.0:

[asrun@asrun-VirtualBox:~/ansible$](mailto:asrun@asrun-VirtualBox:~/ansible$) ansible --version  
**ansible 2.1.0.0**  
config file = /etc/ansible/ansible.cfg  
configured module search path = Default w/o overrides  
[asrun@asrun-VirtualBox:~/ansible$](mailto:asrun@asrun-VirtualBox:~/ansible$) ansible-playbook --private-key sshkeys/my.privatekey pb-jira-create/test.yml  
PLAY [xxxx] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
TASK [setup] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
Enter passphrase for key ‘sshkeys/my.privatekey’:  
ok: [[host.com](http://host.com)]  
TASK [(JIRA) Sample ansible issue] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
fatal: [[host.com](http://host.com)]: FAILED! =\> {“changed”: false, “failed”: true, “msg”: “dictionary update sequence element #0 has length 1; 2 is required”}  
NO MORE HOSTS LEFT \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
to retry, use: --limit @pb-jira-create/test.retry  
PLAY RECAP \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
[host.com](http://host.com) : ok=1 changed=0 unreachable=0 failed=1

Output same playbook in ansible 1.7.2:

[asrun@asrun-VirtualBox:~/ansible$](mailto:asrun@asrun-VirtualBox:~/ansible$) sudo ansible --version  
**ansible 1.7.2**  
[asrun@asrun-VirtualBox:~/ansible$](mailto:asrun@asrun-VirtualBox:~/ansible$) ansible-playbook --private-key sshkeys/my.privatekey pb-jira-create/test.yml  
PLAY [xxxx] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
GATHERING FACTS \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
Enter passphrase for key ‘sshkeys/my.privatekey’:  
ok: [[host.com](http://host.com)]  
TASK: [(JIRA) Sample ansible issue] \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
changed: [[host.com](http://host.com)]  
PLAY RECAP \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*  
[host.com](http://host.com) : ok=2 changed=1 unreachable=0 failed=0

Can anyone confirm jira module still working in 2.1.0.0?

Thank you very much

Ivo

---

<div class="post-metadata">

**Author:** ![j.r.hawkesworth](https://avatars.discourse-cdn.com/v4/letter/j/a3d4f5/32.png) [@j.r.hawkesworth](https://forum.ansible.com/u/j.r.hawkesworth)\
**Post date:** [July 13, 2016, 12:35pm UTC](https://forum.ansible.com/t/create-jira-issue-in-ansible/22007/2 "2016-07-13T12:35:54Z")

</div>

I think I had something like this. I think I fixed it by changing to ‘yaml style’ arguments instead of the key=value arguments. So try something like:

jira:  
description:something  
issuetype: Bug  
operation: create  
password: XXXX  
project: xxx  
summary:test  
uri: [https://hostname.com](https://hostname.com/)  
username: XXX

I am running 2.0.0.2 right now actually, so possibly different in 2.1

Hope this helps

---

<div class="post-metadata">

**Author:** ![Ivo\_Hechmann](https://avatars.discourse-cdn.com/v4/letter/i/91b2a8/32.png) [@Ivo\_Hechmann](https://forum.ansible.com/u/Ivo_Hechmann)\
**Post date:** [July 14, 2016, 7:49am UTC](https://forum.ansible.com/t/create-jira-issue-in-ansible/22007/3 "2016-07-14T07:49:39Z")

</div>

Yay, that did solve the Problem, module works in 2.1.0.0!  
Thank you very much

Ivo