saltstack / saltstack/salt

salt jira.create_issue returning text: Field 'priority' cannot be set. It is not on the appropriate screen, or unknown.

Open
#51,639 18 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

pending-discussion
Dominant language
Python
Stars
15.7k
Forks
5.6k
Avg merge
2d 44m
Merged PRs (30d)
80

Description

saltmaster % sudo salt saltminion1 jira.create_issue NETOPS 'automation test' 'automation test'
saltminion1:
    'jira.create_issue' is not available.

this is on the saltminion in /etc/salt/minion

jira:
  server: https://jira.corp.company.com
  username: salt
  password: pass

Salt Version:
Salt: 2018.3.3

Dependency Versions:
cffi: 1.11.5
cherrypy: Not Installed
dateutil: 2.4.2
docker-py: Not Installed
gitdb: 0.6.4
gitpython: 1.0.1
ioflo: Not Installed
Jinja2: 2.10
libgit2: Not Installed
libnacl: Not Installed
M2Crypto: Not Installed
Mako: 1.0.3
msgpack-pure: Not Installed
msgpack-python: 0.4.6
mysql-python: Not Installed
pycparser: 2.19
pycrypto: 2.6.1
pycryptodome: Not Installed
pygit2: Not Installed
Python: 2.7.12 (default, Dec 4 2017, 14:50:18)
python-gnupg: 0.3.8
PyYAML: 3.13
PyZMQ: 17.1.2
RAET: Not Installed
smmap: 0.9.0
timelib: Not Installed
Tornado: 4.2.1
ZMQ: 4.2.5

System Versions:
dist: Ubuntu 16.04 xenial
locale: ISO-8859-1
machine: x86_64
release: 4.4.0-124-generic
system: Linux
version: Ubuntu 16.04 xenial

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the jira.create_issue entry point and reproduce the command shown against the /etc/salt/minion Jira configuration. Resolve the discrepancy between the reported unavailable execution module and the title's priority-screen error, then verify that creating an issue succeeds without either error.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.