Skip to content

Releases: tenable/integration-jira-cloud

2.1.2

30 Dec 21:56

Choose a tag to compare

What's Changed

New Contributors

Full Changelog: 2.1.1...2.1.2

2.1.1

29 Oct 18:35

Choose a tag to compare

Full Changelog: 2.1.0...2.1.1

2.1.0

22 Aug 16:31

Choose a tag to compare

What's Changed

Full Changelog: 2.0.10...2.1.0

2.0.10

21 Aug 18:30
0b3626c

Choose a tag to compare

  • Corrected Timestamp issue #292
  • Reverted Field casting for floats #294
  • Improved testing

2.0.9

13 Aug 19:52

Choose a tag to compare

  • Improved floating point handling
  • Corrected an issue with Tenable Security Center and null fields
  • Corrected an issue with Tenable Security Center and empty modification dates
  • Added initial support for VPR Thresholding.
  • Fixed minor typos in the field configurations (improved matching for solution and CVE)
  • Added additional testing to ensure that field mapping is being performed correctly.

2.0.8

15 Jul 20:50

Choose a tag to compare

  • Corrected Jira cloud API pagination issue. #280 & #277
  • Added info severity to templated configs #277
  • Corrected SC field issue #276
  • Corrected type issue for SC fields #276 & #272
  • Added missing datepicker field #276

Full Changelog: 2.0.7...2.0.8

2.0.7

20 Jun 13:57

Choose a tag to compare

  • Corrected issue with displaying page size (Tenable SC config)
  • Added --no-cleanup flag to bypass removing the mapping db (for debugging)
  • Added --ignore-last-run flag to ignore the last_run config attribute and instead use the vuln_age setting (for debugging/weird sync issues)

2.0.6

30 May 15:14

Choose a tag to compare

Added support for handling of accepted risks. The default behavior will now treat accepted risks as closed/fixed findings.

2.0.5

22 May 17:32

Choose a tag to compare

  • Corrected exception handling issue that was masked by the thread-execution-worker.

2.0.4

21 May 15:40

Choose a tag to compare

  • Switched the DB model from using the Jira IDs for Issues to Issue Keys instead as the Jira API seemed to not updated things correctly based on ID.