Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-6651

Agile boards have Days in Column value offset by a large incorrect amount

      Summary

      Agile boards have Days in Column value offset by a large incorrect amount

      Steps to Reproduce

      1. Create or use a project with an agile simplified workflow.
      2. Ensure the Days in Column feature is enabled.
      3. On the board, transition an issue to the same status it is currently in.
      4. View Days in Column

      Expected Results

      The Days in Column value remains the same.

      Actual Results

      The Days in Column dots max out and mousing over displays a huge value (e.g. over 16k days).

      Solution / Workaround

      Transition the ticket to other status, and then back to the target column. Consider changing the workflow to prevent recursive transitions.

      Notes/Details

      ".. days in column" data is based on opt_data.issue.timeInColumn.days value and is calculated the following way:

      if (b.timeInColumn) {
      b.timeInColumn.days = Math.floor((b.timeInColumn.durationPreviously + new Date().getTime() - b.timeInColumn.enteredStatus) / a)
      }
      

      which is calculated from timeInColumn value from JSON https://<JIRA>/rest/greenhopper/1.0/xboard/work/allData.json?rapidViewId=<BOARD_ID>.
      Normally, this data looks like:

      "timeInColumn": {
        "enteredStatus": 1442936354000,
        "durationPreviously": 0
      },
      

      in case of an issue was transitioned to the same status it is currently in:

      "timeInColumn": {
        "enteredStatus": 0,
        "durationPreviously": 2301491000
      },
      

      which leads to large opt_data.issue.timeInColumn.days value

        1. bonfire-screenshot-20121115-115417-812.png
          182 kB
          ig
        2. daysincolumn.png
          27 kB
          Danilo Conrad

            [JSWSERVER-6651] Agile boards have Days in Column value offset by a large incorrect amount

            Updated to include Scrum boards since they can also consume this feature.
            Kind regards,
            Martin
            JIRA Agile

            Martin (Inactive) added a comment - Updated to include Scrum boards since they can also consume this feature. Kind regards, Martin JIRA Agile

            We experience a the same effect on Scrum boards.

            Mark Bednarski added a comment - We experience a the same effect on Scrum boards.

            Hi this would be a very useful feature especially for teams transitioning from a physical board where they have red and green dots indicating days worked and not worked

            priya thomas added a comment - Hi this would be a very useful feature especially for teams transitioning from a physical board where they have red and green dots indicating days worked and not worked

            Arun Jose added a comment -

            this is a bug need to be fixed. Its causing confusion regarding days in column

            Hope Developer can fix this issue soon...

            Arun Jose added a comment - this is a bug need to be fixed. Its causing confusion regarding days in column Hope Developer can fix this issue soon...

            For some reason when creating a new issue (and when I move it to a new column) the value of days in column gets set to "-1" and the bar gets maxed out.

            Harri Tunturivuori added a comment - For some reason when creating a new issue (and when I move it to a new column) the value of days in column gets set to "-1" and the bar gets maxed out.

            This small UI defect can really undermine the credibility of a KanBan board to newcomers, because it happens just when starting to work with the board while adding new issues.

            Tested on v6.1.1 and the bug is still there.

            Ricardo Coelho added a comment - This small UI defect can really undermine the credibility of a KanBan board to newcomers, because it happens just when starting to work with the board while adding new issues. Tested on v6.1.1 and the bug is still there.

            David Yu added a comment -

            Seeing this too on some issues on 6.0.6

            David Yu added a comment - Seeing this too on some issues on 6.0.6

              bmccoy bmccoy
              igrunert ig (Inactive)
              Affected customers:
              35 This affects my team
              Watchers:
              39 Start watching this issue

                Created:
                Updated:
                Resolved: