Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-5256

LocMetricsService min and max dates ignored

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Answered
    • Icon: Medium Medium
    • N/A
    • 3.1.3, 3.4.5
    • None

      The following does not work in a FishEye plugin:

      LocMetricsService.QueryParameters locParams = locMetricsService.getQueryBuilder().minDate(firstDay).maxDate(lastDay).build();
Long repoLOC = locMetricsService.getLocCount(repo.getName(), locParams);

      All parameters are valid and firstDay is before lastDay but FishEye ignores the dates and just returns the latest LocCount. Also tried with just minDate and just maxDate to no effect.

      Also raised on Answers: https://answers.atlassian.com/questions/311614/fisheye-locmetricsservice-min-and-max-dates-ignored:

            [FE-5256] LocMetricsService min and max dates ignored

            Marek Parfianowicz added a comment -
            Atlassian Update – 31 January 2020

            Hi everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to close it.

            We want to be clear in managing your expectations. The Fisheye & Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bug Fixing Policy for more details.

            If you still see this bug occurring in the latest release and a fix is very important for you, please don't hesitate to share your feedback in the issue comments and vote on it. We will continue to watch the issue for further updates.

            Kind regards
            Marek Parfianowicz
            Development Team Lead

            Marek Parfianowicz added a comment - Atlassian Update – 31 January 2020 Hi everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to close it. We want to be clear in managing your expectations. The Fisheye & Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bug Fixing Policy for more details. If you still see this bug occurring in the latest release and a fix is very important for you, please don't hesitate to share your feedback in the issue comments and vote on it. We will continue to watch the issue for further updates. Kind regards Marek Parfianowicz Development Team Lead

            Piotr Swiecicki added a comment -

            It seems like a regression introduced around 2.4 version, date criteria indeed seems to be ignored by the service.
            jonathan.cragg, unfortunately I can't provide any exact update on when this issue would be fixed, if at all. According to https://confluence.atlassian.com/display/Support/Atlassian+Bug+Fixing+Policy we assess both value and complexity of each fix. This issue doesn't seem to be highly demanded by our customers, the fix is not trivial, so most likely other issues will be prioritised first in the foreseeable future.
            Kind regards,
            Piotr

            Piotr Swiecicki added a comment - It seems like a regression introduced around 2.4 version, date criteria indeed seems to be ignored by the service. jonathan.cragg , unfortunately I can't provide any exact update on when this issue would be fixed, if at all. According to https://confluence.atlassian.com/display/Support/Atlassian+Bug+Fixing+Policy we assess both value and complexity of each fix. This issue doesn't seem to be highly demanded by our customers, the fix is not trivial, so most likely other issues will be prioritised first in the foreseeable future. Kind regards, Piotr

            Jonathan Cragg added a comment -

            Any update on this ticket please?

            Jonathan Cragg added a comment - Any update on this ticket please?

            Jonathan Cragg added a comment -

            Please can an update be provided on this bug. FishEye is ignoring the first and lastDay dates as per the description above. This is functionality we want to make use of and does not appear to work as 'described on the tin'.

            Jonathan Cragg added a comment - Please can an update be provided on this bug. FishEye is ignoring the first and lastDay dates as per the description above. This is functionality we want to make use of and does not appear to work as 'described on the tin'.

            Alan M added a comment -

            Have you been able to reproduce?

            Alan M added a comment - Have you been able to reproduce?

            Alan M added a comment -

            Subversion, thanks

            Alan M added a comment - Subversion, thanks

            Sten Pittet (Inactive) added a comment -

            Hi alan.mosely,

            Sorry for the late reply. Could you please tell me what SCM you are using for your development?

            Thanks,

            Sten

            Sten Pittet (Inactive) added a comment - Hi alan.mosely , Sorry for the late reply. Could you please tell me what SCM you are using for your development? Thanks, Sten

            Alan M added a comment -

            Can someone pick this up plz?

            Alan M added a comment - Can someone pick this up plz?

              Unassigned Unassigned
              dcf3abfa2cba Alan M
              Affected customers:
              1 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: