deepfence / deepfence/ThreatMapper
jira issue assignee
- Dominant language
- TypeScript
- Stars
- 5.3k
- Forks
- 631
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
in jira integration once configured all the issues appear with assigneed unassigned ; assignee should not be left unassigned and should be configurable while in jira integration
**To Reproduce**
Steps to reproduce the behavior:
1. Integrate jira with the deepfence console
2. run scan
3. and check the jira type that got raised look for assignee it stays unassigned
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Components/Services affected**
- [ ] UI/Frontend
- [ ] API/Backend
**Additional context**
Add any other context about the problem here.
Contributor guide
Assessment
This issue has not been assessed yet.