Error creating Jira issue for T1001 about attack2jira HOT 8 CLOSED

Thanks for reporting this @SkiddyBargins . I remember this issue and I thought I fixed it. I will take a look. Just to confirm, are you using the latest release ? Please make sure you are.

from attack2jira.

@SkiddyBargins , I just tested the latest version from master a couple of times and its working for me. As mentioned before, I did see this issue on the previous version. Can you please

1. Make sure you are using the latest version from the master branch
2. If the issue still persists, post the script output here.

Thanks!

from attack2jira.

@SkiddyBargins did you test ?

from attack2jira.

Yes,

Getting the below now which looks like the 401 error.
Validated permissions and access.

[!] Success!
[*] Creating the Att&ck project...
[!] Unauthorized. Probably not enough permissions :(

from attack2jira.

Looks like a 405 error hitting '/rest/simplified/latest/project'

from attack2jira.

Looks like a 405 error hitting '/rest/simplified/latest/project'

Just to double check, your project link has the s in the protocol of the URL (as in https)?

from attack2jira.

I'm running into this same issue. I tried running this in a free trial version and everything went smoothly. When trying to run in on my company's instance I got the following error. I have admin rights in both instances.

[*] Creating Jira issues for ATT&CK's techniques... [!] Error creating Jira issue for T1001 {"errorMessages":[],"errors":{"customfield_10110":"Field 'customfield_10110' cannot be set. It is not on the appropriate screen, or unknown.","customfield_10111":"Field 'customfield_10111' cannot be set. It is not on the appropriate screen, or unknown.","customfield_10112":"Field 'customfield_10112' cannot be set. It is not on the appropriate screen, or unknown.","customfield_10113":"Field 'customfield_10113' cannot be set. It is not on the appropriate screen, or unknown.","customfield_10114":"Field 'customfield_10114' cannot be set. It is not on the appropriate screen, or unknown."}}

EDIT: I am running the latest version from the master branch

from attack2jira.

I tested this again with a new API key and it worked.

Not sure if the issue was with Jira Cloud, but previously I used three keys and it failed.

from attack2jira.