Add team-managed Jira projects

[chrischan753]

⚠️ 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

Is your feature request related to a problem? Please describe
A clear and concise description of what the problem is.

I'm currently unable to create Jira issues in team-managed (formerly next-gen) Jira projects. This limitation prevents me from seamlessly integrating my findings into our usual issue-tracking process. As a result, I have to rely on manual workarounds or separate project configurations, which is inefficient and increases the risk of missing important updates or tasks.

Describe the solution you'd like
A clear and concise description of what you want to happen.

As a security analyst, I want to create issues directly in our team-managed Jira projects so that all vulnerabilities are tracked in one streamlined workflow, reducing manual overhead and minimizing the risk of missed updates.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you have considered.

I initially tried setting up Jira as a company-managed project, but this approach presented compliance obstacles because I’m unable to create or modify fields at will. Consequently, I looked into using a team-managed Jira project instead, which would give me the flexibility I need while ensuring I’m not interfering with the organization's established processes and policies.

Thanks.

[valentijnscholten]

similar to #5179 #7360

can you let us know what errors you are seeing?

[chrischan753]

hey @valentijnscholten
thanks for the review.

the error i see is:

If i save the product-settings:

[valentijnscholten]

Could you check the errors from the logs? If you're running the docker compose setup, you can view them with docker compose logs or tail them with docker compose logs -f. We know that next gen projects are slightly different, but it's good to have some real world error messages to get a feel for what's wrong.

[chrischan753]

Hey sry for the delayed answer. here are the logs for saving the product, but the error message is the same. How can I increase the log level? maybe that would show some more information?!

wsgi-1 | [pid: 1|app: -|req: -/-] 24.134.49.93 (admin) {60 vars in 1526 bytes} [Fri Jan 10 07:11:47 2025] GET /product/2 => generated 97621 bytes in 562 msecs (HTTP/1.1 200) 8 headers in 377 bytes (1 switches on core 1) nginx-1 | 24.134.49.93 - - [10/Jan/2025:07:11:47 +0000] "GET /product/2 HTTP/1.1" 200 13569 "https://<url>/product" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36" "-" uwsgi-1 | [pid: 31|app: -|req: -/-] 24.134.49.93 (admin) {60 vars in 1538 bytes} [Fri Jan 10 07:11:50 2025] GET /product/2/edit => generated 103727 bytes in 199 msecs (HTTP/1.1 200) 8 headers in 378 bytes (1 switches on core 0) nginx-1 | 24.134.49.93 - - [10/Jan/2025:07:11:50 +0000] "GET /product/2/edit HTTP/1.1" 200 14132 "https://<url>/product/2" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36" "-" uwsgi-1 | [pid: 31|app: -|req: -/-] 24.134.49.93 (admin) {58 vars in 1379 bytes} [Fri Jan 10 07:12:00 2025] GET /alerts/count => generated 14 bytes in 34 msecs (HTTP/1.1 200) 7 headers in 212 bytes (1 switches on core 1) nginx-1 | 24.134.49.93 - - [10/Jan/2025:07:12:00 +0000] "GET /alerts/count HTTP/1.1" 200 14 "https://<url>/product/2/edit" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36" "-" nginx-1 | 24.134.49.93 - - [10/Jan/2025:07:12:10 +0000] "GET /alerts/count HTTP/1.1" 200 14 "https://<url>/product/2/edit" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36" "-" uwsgi-1 | [pid: 1|app: -|req: -/-] 24.134.49.93 (admin) {58 vars in 1379 bytes} [Fri Jan 10 07:12:10 2025] GET /alerts/count => generated 14 bytes in 33 msecs (HTTP/1.1 200) 7 headers in 212 bytes (1 switches on core 0)
uwsgi-1 | [10/Jan/2025 07:12:13] WARNING [dojo.jira_link.helper:1162] Failed retrieving field metadata from Jira version: (1001, 0, 0), project: SEC, issue type: Epic. Project misconfigured or no permissions in Jira ?
uwsgi-1 | [pid: 1|app: -|req: -/-] 24.134.49.93 (admin) {68 vars in 1739 bytes} [Fri Jan 10 07:12:11 2025] POST /product/2/edit => generated 105447 bytes in 1236 msecs (HTTP/1.1 200) 8 headers in 378 bytes (1 switches on core 1) nginx-1 | 24.134.49.93 - - [10/Jan/2025:07:12:13 +0000] "POST /product/2/edit HTTP/1.1" 200 14420 "https://<url>/product/2/edit" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36" "-"