Sonar

Support of differential views (e.g. : changes during the last 7, 30 and 90 days) by core services

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 2.5
  • Component/s: Differential Views, Web
  • Labels:
    None
  • Number of attachments :
    0

Description

Currently, quality information provided by Sonar is very static and can't allow to get a clear insight on what happened for instance during the last 30 days. Differential views must allow to switch from classical static measures to differential measures.

In all Sonar core services supporting this new feature, a dropdown list will be available to select the time interval. This dropdown list will have tree values and the first two ones will be the same for all projects. For instance 30 days and 90 days. Those two first time intervals will be configurable in the Settings page.

The third value will be configurable by project and by default will be 'last event'. So by default, the current snapshot will be compared with the last snapshot having an event.

The value of this event will be configurable by project (e.g. : '2.5', 'offshoring of the project', ...).

Issue Links

This issue is duplicated by:
SONAR-1603 Difference Viewer Major Closed
This issue relates to:
SONAR-1450 Add support for incremental review of incoming violations Major Closed
This issue is related to:
SONAR-369 Add a two date pickers to fix beetween two dates to caculate color on the treemap (by default, it is the last date) Major Closed
SONAR-628 Time Machine - Comparison required at file level Major Closed
SONAR-1160 The 10 "last" Rule violations Major Closed
SONAR-837 Evolve Sonar plugins in order to handle an optional list of files to process Major Closed
SONAR-1958 Being able to define an alert on differential measures Major Closed
This issue is depended upon by:
SONARPLUGINS-348 Add commit count for past periods Major Closed
SONAR-1352 Create alerts based on differential view measures Major Open
SONARPLUGINS-539 Collect active developer metric Major Open

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Mihai Campean added a comment -

I am going to work on this, since it is connected with SONAR-837, that is if nobody else did work on it already.

Show
Mihai Campean added a comment - I am going to work on this, since it is connected with SONAR-837, that is if nobody else did work on it already.
Hide
Permalink
Mihai Campean added a comment -

Since lately I have been pretty busy at work and at home, my time doesn't permit me to contribute to all the things I would like anymore, so for a while I won't be able to do any work on Sonar issues.
Sorry for the inconveniences I may have caused and I will let you know if I'll be available any time soon.

Show
Mihai Campean added a comment - Since lately I have been pretty busy at work and at home, my time doesn't permit me to contribute to all the things I would like anymore, so for a while I won't be able to do any work on Sonar issues. Sorry for the inconveniences I may have caused and I will let you know if I'll be available any time soon.
Hide
Permalink
julien coulmeau added a comment - - edited

Hi,

As I commented in SONAR-1160, this feature will be extremely useful if it allows to display the changes between the two dates (a delta of violations for instance and allow to display only new violations).

The reason for a delta is for instance (it is the case in my company), you have heavy existing projects that you do not want to destabilize with fixes related to Sonar violations (at least not on the short term).
On the other hand, you want to make sure that any new code committed follows strict rules.

Julien

Show
julien coulmeau added a comment - - edited Hi, As I commented in SONAR-1160, this feature will be extremely useful if it allows to display the changes between the two dates (a delta of violations for instance and allow to display only new violations). The reason for a delta is for instance (it is the case in my company), you have heavy existing projects that you do not want to destabilize with fixes related to Sonar violations (at least not on the short term). On the other hand, you want to make sure that any new code committed follows strict rules. Julien
Hide
Permalink
denis krizanovic added a comment -

Hi guys,

Can we add 14 days to the drop down too.. As most agile places will have 2 week iterations, 14 days will help us understand what state the code base is in after an iteration.

thanks.

Show
denis krizanovic added a comment - Hi guys, Can we add 14 days to the drop down too.. As most agile places will have 2 week iterations, 14 days will help us understand what state the code base is in after an iteration. thanks.
Hide
Permalink
Evgeny Mandrikov added a comment -

Hi Denis,

If my understanding correct, then if we can implement this feature for "30 days", then in future we can make this configurable. As I know we prefer baby steps in implementing new features instead of trying to cover all user needs.

Show
Evgeny Mandrikov added a comment - Hi Denis, If my understanding correct, then if we can implement this feature for "30 days", then in future we can make this configurable. As I know we prefer baby steps in implementing new features instead of trying to cover all user needs.
Hide
Permalink
denis krizanovic added a comment -

Hi Evgeny,

I understand that configurability will come. I was just hopping to add another pre-configured number, so that it ran 7, 14, 30, 90, such that I can get immediate use of it.

I do understand where you're coming from. If its too much trouble, then I wait.

Show
denis krizanovic added a comment - Hi Evgeny, I understand that configurability will come. I was just hopping to add another pre-configured number, so that it ran 7, 14, 30, 90, such that I can get immediate use of it. I do understand where you're coming from. If its too much trouble, then I wait.
Hide
Permalink
Roman Ivanov added a comment - - edited

Hi Eugene,

Our company come to Sonar JIRA to request/discuss similar issue.
We need to see History thread (day by day), see what is become appear and fixed in Violations and who is to blame.
Additionally to see changes tracing page by click over colored triangles (that shows changes).

We make a step further and we want to collaborate with Sonar command to help you implement this feature, by contributing patches. Please contact with me for constructive discussion.

Show
Roman Ivanov added a comment - - edited Hi Eugene, Our company come to Sonar JIRA to request/discuss similar issue. We need to see History thread (day by day), see what is become appear and fixed in Violations and who is to blame. Additionally to see changes tracing page by click over colored triangles (that shows changes). We make a step further and we want to collaborate with Sonar command to help you implement this feature, by contributing patches. Please contact with me for constructive discussion.
Hide
Permalink
Freddy Mallet added a comment -

Hello Roman, I guess you're talking about something pretty similar to SONAR-1450/SONAR-1160 which should be fixed with Sonar 2.5. If not, please start a thread of discussions on the development mailing list : http://www.sonarsource.org/support

Show
Freddy Mallet added a comment - Hello Roman, I guess you're talking about something pretty similar to SONAR-1450/SONAR-1160 which should be fixed with Sonar 2.5. If not, please start a thread of discussions on the development mailing list : http://www.sonarsource.org/support
Hide
Permalink
Simon Brandhof added a comment -

First draft : https://skitch.com/simon.brandhof/rdbh4/variations-1

Show
Simon Brandhof added a comment - First draft : https://skitch.com/simon.brandhof/rdbh4/variations-1
Hide
Permalink
Mallari Kulkarni added a comment -

Simon
Need some clarification on the dropdown. The values are dependent when the last time violations build is executed.

i.e If the user selects 15 days, and if the violation build is not executed, then the system may not be able to show these results.

Show
Mallari Kulkarni added a comment - Simon Need some clarification on the dropdown. The values are dependent when the last time violations build is executed. i.e If the user selects 15 days, and if the violation build is not executed, then the system may not be able to show these results.
Hide
Permalink
Simon Brandhof added a comment -

Labels in select-box must be improved. Selecting a number of days means "number of days before analysis". In won't be disturbing in continuous inspection environments, when projects are daily analyzed.

Show
Simon Brandhof added a comment - Labels in select-box must be improved. Selecting a number of days means "number of days before analysis". In won't be disturbing in continuous inspection environments, when projects are daily analyzed.
Hide
Permalink
Mallari Kulkarni added a comment -

One suggestion is --> Instead of displaying 30 days or 90 days,the dropdown could have previous sonar-build execution date.

Show
Mallari Kulkarni added a comment - One suggestion is --> Instead of displaying 30 days or 90 days,the dropdown could have previous sonar-build execution date.
Hide
Permalink
Mallari Kulkarni added a comment -

Is this change hosted on http://nemo.sonarsource.org/drilldown/violations/78577?

Show
Mallari Kulkarni added a comment - Is this change hosted on http://nemo.sonarsource.org/drilldown/violations/78577?
Hide
Permalink
Freddy Mallet added a comment -

Not yet Mallari, Sonar 2.5 has not been yet installed on Nemo.

Show
Freddy Mallet added a comment - Not yet Mallari, Sonar 2.5 has not been yet installed on Nemo.
Hide
Permalink
Mallari Kulkarni added a comment -

Thought it shows the number violations increased on the dashboard, when I go for drilldown and select " add over 30 days", I donot get the difference (newly added) violations.
Is this feature not enabled?

Show
Mallari Kulkarni added a comment - Thought it shows the number violations increased on the dashboard, when I go for drilldown and select " add over 30 days", I donot get the difference (newly added) violations. Is this feature not enabled?
Hide
Permalink
Simon Brandhof added a comment -

Indeed there's a bug in RC1. It has been fixed for final release. Thanks for the feedback.

Show
Simon Brandhof added a comment - Indeed there's a bug in RC1. It has been fixed for final release. Thanks for the feedback.

People

Vote (11)
Watch (6)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.