Jira Setup for Vulnerability Management
Budget: ₹10,000 – ₹35,000 INR
I currently log every vulnerability in a single Excel sheet. I now want that whole process living inside Jira so my IT team can collaborate, track status, and report in real time. We already have a Jira Cloud instance; what I need is a turnkey configuration that feels purpose-built for vulnerability management rather than generic issue tracking.
Here is what success looks like to me:
• Vulnerability tracking – A dedicated project (or projects) with custom issue types and fields that mirror the data points in my spreadsheet, plus severity-based SLAs.
• Workflow automation – Transitions that enforce our remediation flow (Open → Triage → In Progress → Ready for Test → Closed) and auto-assign tickets, set due dates, and send reminders using Jira Automation rules.
• Custom dashboards – At-a-glance views for the IT team showing open items by severity, time-to-close metrics, and SLA breaches, all exportable for management reports.
• Data migration – Clean import of the existing Excel sheet so we don’t lose history.
• Permission scheme – Only the IT team needs edit rights; everyone else should have view-only access.
• Clear documentation – A short guide or screen-recording that explains the workflow, dashboards, and how to raise new vulnerabilities.
I will give you the spreadsheet, admin access to a sandbox project, and any field names you need. Deliverables are accepted once the project is live in our production Jira and my team can reproduce the end-to-end flow without issues.
Here is what success looks like to me:
• Vulnerability tracking – A dedicated project (or projects) with custom issue types and fields that mirror the data points in my spreadsheet, plus severity-based SLAs.
• Workflow automation – Transitions that enforce our remediation flow (Open → Triage → In Progress → Ready for Test → Closed) and auto-assign tickets, set due dates, and send reminders using Jira Automation rules.
• Custom dashboards – At-a-glance views for the IT team showing open items by severity, time-to-close metrics, and SLA breaches, all exportable for management reports.
• Data migration – Clean import of the existing Excel sheet so we don’t lose history.
• Permission scheme – Only the IT team needs edit rights; everyone else should have view-only access.
• Clear documentation – A short guide or screen-recording that explains the workflow, dashboards, and how to raise new vulnerabilities.
I will give you the spreadsheet, admin access to a sandbox project, and any field names you need. Deliverables are accepted once the project is live in our production Jira and my team can reproduce the end-to-end flow without issues.
Related categories:
Project Management
Excel
Documentation
Agile Project Management
Automation
Change Management