Update helper.py to fix #8785

[devsecopsale]

this will fix #8785

⚠️ Note on feature completeness ⚠️

We are narrowing the scope of acceptable enhancements to DefectDojo in preparation for v3. Learn more here:
https://github.com/DefectDojo/django-DefectDojo/blob/master/readme-docs/CONTRIBUTING.md

Description

this will fix #8785 , by adding the jira.project default_assignee (when defined) to the issue creation api call instead of adding a second step to do it.

Test results

this was tested in 2.23.2 and allowed to create issues in a Jira project where no 'unassigned' or 'automatic' assignee was allowed.

Documentation

Checklist

This checklist is for your information.

• Make sure to rebase your PR against the very latest dev.
• Features/Changes should be submitted against the dev.
• Bugfixes should be submitted against the bugfix branch.
• Give a meaningful name to your PR, as it may end up being used in the release notes.
• Your code is flake8 compliant.
• Your code is python 3.11 compliant.
• If this is a new feature and not a bug fix, you've included the proper documentation in the docs at https://github.com/DefectDojo/django-DefectDojo/tree/dev/docs as part of this PR.
• Model changes must include the necessary migrations in the dojo/db_migrations folder.
• Add applicable tests to the unit tests.
• Add the proper label to categorize your PR.

Extra information

Please clear everything below when submitting your pull request, it's here purely for your information.

Moderators: Labels currently accepted for PRs:

• Import Scans (for new scanners/importers)
• enhancement
• performance
• feature
• bugfix
• maintenance (a.k.a chores)
• dependencies
• New Migration (when the PR introduces a DB migration)
• settings_changes (when the PR introduces changes or new settings in settings.dist.py)

Contributors: Git Tips

Rebase on dev branch

If the dev branch has changed since you started working on it, please rebase your work after the current dev.

On your working branch mybranch:

git rebase dev mybranch

In case of conflict:

 git mergetool
 git rebase --continue

When everything's fine on your local branch, force push to your myOrigin remote:

git push myOrigin --force-with-lease

To cancel everything:

git rebase --abort

Squashing commits

git rebase -i origin/dev

• Replace pick by fixup on the commits you want squashed out
• Replace pick by reword on the first commit if you want to change the commit message
• Save the file and quit your editor

Force push to your myOrigin remote:

git push myOrigin --force-with-lease

[Maffooch]

Flake8 is very unhappy :/ please take a look

[devsecopsale]

Flake8 is very unhappy :/ please take a look

For what I could see, none of the warnings come from the changes I made.

[devsecopsale]

Flake8 is very unhappy :/ please take a look

For what I could see, none of the warnings come from the changes I made.

hi @Maffooch , just checking if you had the chance to read my last response. thanks

[Maffooch]

Hi @devsecopsale apologies, I missed your response. It does look like none of the errors flake8 are reporting are a result of changes you made. Unfortunately, I am unable to merge the PR until all checks are passing

[github-actions]

python: can't open file '/home/runner/work/django-DefectDojo/django-DefectDojo/.github/scripts/git_protect.py': [Errno 2] No such file or directory

[devsecopsale]

Hi @Maffooch , I fixed flake8 errors too. There's now an error reported by git_protect.py. Not a clue why this is failing.

Run python .github/scripts/git_protect.py 1c8e375 86e5d68 --comment-only &> output.txt
Error: Process completed with exit code 2.

[devsecopsale]

hi @Maffooch , any idea of what this check is about? can this be rerun?

[mtesauro]

@devsecopsale About that test - see here: #8974

It allows us to signal contributors that they are touching files that we may be actively working on updating/doing a re-write. I don't have time right now to review this PR but that test isn't something you can "pass" short of removing the file(s) from the PR which probably isn't possible for this one.

Think of this as a heads-up that we're going to look a bit more closely at this PR vs a parser PR for example.

[mtesauro]

Approved

[devsecopsale]

@dougmorato , @Juu: I just need 2 more approvals to merge. Thank you