mvelazc0 / attack2jira

attack2jira automates the process of standing up a Jira environment that can be used to track and measure ATT&CK coverage
BSD 3-Clause "New" or "Revised" License
111 stars 29 forks source link

Error creating Jira issue for T1001 #15

Closed SkiddyBargins closed 3 years ago

SkiddyBargins commented 3 years ago

I am installing on Jira Software Cloud with it tripping up on the below

[*] Creating Jira issues for ATT&CK's techniques... [!] Error creating Jira issue for T1001 {"errorMessages":[],"errors":{"customfield_10038":"Field 'customfield_10038' cannot be set. It is not on the appropriate screen, or unknown.","customfield_10034":"Field 'customfield_10034' cannot be set. It is not on the appropriate screen, or unknown.","customfield_10035":"Field 'customfield_10035' cannot be set. It is not on the appropriate screen, or unknown.","customfield_10036":"Field 'customfield_10036' cannot be set. It is not on the appropriate screen, or unknown.","customfield_10037":"Field 'customfield_10037' cannot be set. It is not on the appropriate screen, or unknown."}}

mvelazc0 commented 3 years ago

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.

mvelazc0 commented 3 years ago

@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!

image

mvelazc0 commented 3 years ago

@SkiddyBargins did you test ?

SkiddyBargins commented 3 years ago

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 :(

SkiddyBargins commented 3 years ago

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

PolarBearGod commented 3 years ago

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)?

ScooterSec commented 3 years ago

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

SkiddyBargins commented 3 years ago

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.