SonarQube: Community-Edition
Hello.
When a security hotspot is on status reviewed, the json does not contain a closeDate but only an updateDate.
For my understanding hotspots with status reviewed should have a closeDate.
Do you agree on this and is it possible to change this?
Best
Hey there.
While non-hotspots (issues) have the concept of being Closed, hotspots do not. Hotspots have many statuses but are never officially “closed”. It wouldn’t make sense to a closeDate. Maybe it would make sense to have a reviewedDate, however, if you need to pull a report and figure out when a Hotspot received its status, you’ll have to use updateDate.
Hey.
Thank you for answering.
Is it then possible for your team to add a reviewedDate to the json of the security hotspots?
Best
@Colin sorry for bothering, but is it possible to add a reviewedDate to the json of the security hotspots?
Hello Simon,
Can you help us understand why ‘updateDate’ fulfills your requirement?
can you share what you are trying to accomplish?
@vivek.reghunath Hi Vivek,
I’m trying to get the date when a hotspot was set to reviewed. I cannot use updateDate because after a hotspot has been set to reviewed, someone could still add a comment to the hotspot which would cause the updateDate to change and thus no longer be the date when the hotspot was set to reviewed status.
For issues this is easy to find out as I can just access the closeDate. I would like to have something similar for hotspots, for example a reviewedDate.
@Colin @vivek.reghunath or somebody else.
Please confirm or reject my proposal to add a reviewedDate to the json of a hotspot.
My claim is:
Currently there is no option to get out of the json the exact date when a hotspot was set to reviewed. (I cannot use updateDate because after a hotspot has been set to reviewed, someone could still add a comment to the hotspot which would cause the updateDate to change and thus no longer be the date when the hotspot was set to reviewed status.)
This is important because knowing the reviewedDate helps for example to identify hotspots that have been incorrectly or accidentally set to reviewed by other users. Issues already have this feature with the closeDate. I’m asking to also add this to the hotspot json in the form of a reviewedDate.
Hey @simonvonroenn
No decision has been taken as of today. This is a community forum where folks are welcome to suggest ideas; if others face the same need, they can comment and help an issue build traction… but we are not here to take every suggestion and issue a yes/no as soon as possible.