edgescan for Jira Cloud

We are extremely dissatisfied with the functionality and behavior of the recently installed plugin in our Jira environment. Upon configuring the plugin with a specific issue type in one Jira project, the same configuration is automatically applied to all subsequent linked projects without our consent or intervention. This unexpected behavior is highly disruptive and undermines our project management processes. Additionally, the plugin does not provide the necessary flexibility to edit or update issue types and related configurations. This significant limitation severely restricts our ability to manage projects effectively within Jira. The most concerning aspect is that the plugin requires continuous support from the vendor for even basic maintenance and adjustments. This dependency makes the plugin highly inefficient and unsustainable for long-term use in our environment. We strongly advise others to carefully evaluate this plugin before considering its installation, as its current design and functionality present considerable challenges for effective Jira project management.

• 

  Edgescan

  Thank you for taking the time to share your feedback — we take every review seriously, and we'd like to respectfully address the points raised, as we believe there may have been some misunderstanding about how the plugin is designed to operate.

  1. "Configuration is automatically applied to all subsequent linked projects." This is not how the plugin works. Each Jira project is linked to Edgescan independently via Project Administration → Link to Edgescan, and every project link has its own configuration — including linked assets, risk-to-priority mappings, issue type on create, status on create, status on close, board configurations, components, and title templates. Changing the configuration in one project does not alter the configuration of any other linked project. If you were seeing configuration appear to propagate, we would very much like to investigate — please open a support ticket so we can look at the specific project links involved.

  2. "The plugin does not provide the flexibility to edit or update issue types and related configurations." All of these settings are fully editable at any time from the project configuration page by any Jira user with project admin permissions. You can change the issue type, reassign risk-to-priority mappings, update status-on-create / status-on-close transitions, add or remove linked assets, toggle issue deletion, select components, and configure per-board behaviour — all without vendor involvement and without reinstalling the plugin. Changes take effect on the next sync.

  3. "The plugin requires continuous vendor support for basic maintenance and adjustments." Day-to-day configuration, sync scheduling, asset linking, and workflow mapping are all self-service inside Jira. Vendor support is only needed for things outside the plugin's control — for example, API token issues on the Edgescan side, or non-standard Jira workflow states that block a transition.

  Since this review was posted we have also shipped further improvements — multi-board support per project, more granular control over which vulnerabilities sync, configurable issue titles, improved description updates on sync, and better handling of issues deleted manually in Jira.

  If you are still using the plugin, we would genuinely welcome the opportunity to walk through your setup with you and make sure it's working the way you need. Please reach out to our support team and we'll be happy to help.

  — The Edgescan team