Events on Dashboard confused for same project dates

Details

  • Type: Improvement Improvement
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.8
  • Fix Version/s: 2.12
  • Component/s: Events
  • Labels:
    None
  • Environment:
    Windows, Maven CLI, Derby, SVN

Description

When old projects are imported using the -Dsonar.projectDate advanced parameter, and the projectDate is the same for multiple versions, then the "Events" displayed on the Dashboard is being confused and shows the versions in the wrong order. I assume that it's caused because the ordering solely takes place on the date column and has no second order column. I think it should sort by project date (descending) first and then by versions numer (descending).

Note that the project date was given with only yyyy-mm-dd, but no time. Hence, two versions built on the same day have the same timestamp (.e.g 2008-10-11T00:00:00)

Issue Links

depends upon

Bug - A problem which impairs or prevents the functions of the product. SONAR-2811 Time Machine won't compare to previous versions if said version has been manually modified.

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
relates to

Improvement - An improvement or enhancement to an existing feature or task. SONAR-2919 Refactor event handling in Sonar Web

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Freddy Mallet added a comment -

I assume you set the priority to Trivial as it unusual to to release to major version the same day (0.4.0 and 0.9.0 in your example) ? To fix this ticket, we can offer to optionally specify a Time (yyyy-mm-dd-hh-mm-ss) instead of a Date (yyyy-mm-dd) ?

Show
Freddy Mallet added a comment - I assume you set the priority to Trivial as it unusual to to release to major version the same day (0.4.0 and 0.9.0 in your example) ? To fix this ticket, we can offer to optionally specify a Time (yyyy-mm-dd-hh-mm-ss) instead of a Date (yyyy-mm-dd) ?
Hide
Permalink
Mike R. Haller added a comment -

Yes, that would be nice. I think parsing the projectDate including with the time part would also make it more suitable for automated scripts. For example using the SVN metadata's last commit date as the projectDate (that's usually the build server performing the release:prepare and creating the SVN tag).

Show
Mike R. Haller added a comment - Yes, that would be nice. I think parsing the projectDate including with the time part would also make it more suitable for automated scripts. For example using the SVN metadata's last commit date as the projectDate (that's usually the build server performing the release:prepare and creating the SVN tag).
Hide
Permalink
Fabrice Bellingard added a comment -

It is now possible to specify 'sonar.projectDate' as a standard ISO time (e.g. "2011-10-25T05:45:10+0100").

Show
Fabrice Bellingard added a comment - It is now possible to specify 'sonar.projectDate' as a standard ISO time (e.g. "2011-10-25T05:45:10+0100").
Hide
Permalink
Freddy Mallet added a comment -

Manually tested !

Show
Freddy Mallet added a comment - Manually tested !
Hide
Permalink
Fabrice Bellingard added a comment -

ITs done.

Show
Fabrice Bellingard added a comment - ITs done.

People

  • Assignee:
    Fabrice Bellingard
    Reporter:
    Mike R. Haller
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: