-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
errors:{"issuetype":"The issue type selected is invalid."}} #28
Comments
You'll likely need to manually select the issue types. Refer to the info here: |
Hi Steve, Thanks for that. So I made the following changes: issue_types:
- name: Task
jira_id: 18
type: standard
search:
- Tenable Plugin ID
- name: Sub-task
type: subtask
jira_id: 19
search:
- Tenable Platform
- Tenable Plugin ID
- Tenable Asset UUID
- Device IPv4 Addresses
- Device IPv6 Addresses
- Vulnerability Port
- Vulnerability Protocol
screen:
jira_ids:
- 14632
- 14633 However I know receive the following error:
|
I wonder if I should remove the name bit from the config file? screen: name: tabs: |
That error says that the custom fields aren't associated to those screens. Did you attempt to let the code figure out the screen jira_ids? |
Yeah, the first change that I made was just the task and sub task ids but received the same error. |
Looking at the debug log, it correctly recognises the screens: |
try different issuetype IDs (if you have multiple Task and SubTask issuetypes). Most if the issues I have seen with Jira have been around Issuetypes and how widely the issuetype names are duplicated. |
Hey Steve, I just checked and we only have one of each i.e. 1 task and 1 subtask issue type and their ids are 18 and 19 respectively |
what are the debug logs saying? The only other issue is that the screen selection is wrong.
|
2020-04-01 11:20:08,929 root INFO Tenable2JiraCloud Version 1.1.3 |
I tried looking at that and I can't see anything wrong with the screen selection i.e. it's the right screen for the project created by the script itself |
Oh another thing what I forgot to mention was that it creates 2 issues and then throws up that error on a particular vulnerability. I created a new group manually and then tried running the script, again same issue, it stops at a particular vulnerbility. I will attach the debug log below |
thats really odd. |
|
Do you know if there are any specific api related permissions that need to be turned on for creating issues? I don't know, I am thinking it creates the first few issues and then realises "Oh hold on! this person doesn't have permissions!, we need to block the rest" - sorry if it sounds a bit stupid but I seriously can't think of anything else |
Hey Steve, Relieve!!!! I cracked it, it was a permission thing causing this. I went in and gave the API user all the permissions relating to issues and that did the trick. |
awesome! mind detailing what perms you needed to give the user? I can update our docs to leverage that. |
Sure! I gave the following permissions: or you could just use the 'Grant Permissions' wizard within Jira cloud and grant all permissions related to 'Issues' |
@dil-ddsouza did you assign the API user these permissions directly, or via group membership? |
Via the group permission option, which allows the grant permissions wizard |
Since you determined the user didn't have proper privileges, did you initially create a user with site admin privileges as mentioned in this guide? JIRA admin profiles seem convoluted. |
Hi Steven,
We were successful when we used the script on our test jira instance. However now when we moved to our production Jira instance, we get this error when running the script. I have made sure that the settings is like for like with the test jira project:
2020-04-01 09:29:22,961 urllib3.connectionpool DEBUG https://production.atlassian.net:443 "POST /rest/api/3/issue?update_history=False HTTP/1.1" 400 None
2020-04-01 09:29:22,963 restfly.errors.BadRequestError ERROR [400: POST] https://production.atlassian.net/rest/api/3/issue?update_history=False body=b'{"errorMessages":[],"errors":{"issuetype":"The issue type selected is invalid."}}'
Any help and guidance would be appreciated.
The text was updated successfully, but these errors were encountered: