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

"for Kanban boards, the dots at the bottom of each issue indicate the number of days the issue has been in its current column. Hover over the dots to see the total number of days" - day's are not shown here in hoover

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low (View bug fix roadmap)
    • None
    • None
    • None
    • None

      NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.

      Beschreibung eingeben

            [JSWSERVER-10149] "for Kanban boards, the dots at the bottom of each issue indicate the number of days the issue has been in its current column. Hover over the dots to see the total number of days" - day's are not shown here in hoover

            Mykenna Cepek added a comment -

            I have a team complaining about the way the dots work. They're using a Scrum board, so issues in the Backlog are almost always in the To Do status. Issues are typically in the Backlog for some weeks before making it into a Sprint. This seems typical for most Scrum teams.

            However, when an issue is moved into a Sprint from the Backlog, the dots are not reset to zero. So when a Sprint starts, many issues in the To Do column show many dots, or even a full range of dots, even though this is the "first day the issue has been in the To Do column" for any Sprint. That doesn't seem like correct behavior.

            Folks might also want to reference this KB article, which contains a couple of workarounds that might help in some situations (I'm awaiting admin help to explore them):

            When the "Days in column" setting is enabled, an incorrect number of dots is displayed in the Sprint cards

            Mykenna Cepek added a comment - I have a team complaining about the way the dots work. They're using a Scrum board, so issues in the Backlog are almost always in the To Do status. Issues are typically in the Backlog for some weeks before making it into a Sprint. This seems typical for most Scrum teams. However, when an issue is moved into a Sprint from the Backlog, the dots are not reset to zero. So when a Sprint starts, many issues in the To Do column show many dots, or even a full range of dots, even though this is the "first day the issue has been in the To Do column" for any Sprint. That doesn't seem like correct behavior. Folks might also want to reference this KB article, which contains a couple of workarounds that might help in some situations (I'm awaiting admin help to explore them): When the "Days in column" setting is enabled, an incorrect number of dots is displayed in the Sprint cards
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2850756 ] New: JAC Bug Workflow v3 [ 2932546 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545416 ] New: JAC Bug Workflow v2 [ 2850756 ]

            Chris Garvey added a comment -

            Is there a way to configure how the dots work? We don't want them to show cumulative or total time in a column, just the amount of time they have been in a column since they were last put there. 

            Chris Garvey added a comment - Is there a way to configure how the dots work? We don't want them to show cumulative or total time in a column, just the amount of time they have been in a column since they were last put there. 
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549635 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2545416 ]
            jonah (Inactive) made changes -
            Description Original: Beschreibung eingeben New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Software Server*. Using *JIRA Software Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSWCLOUD-10149].
              {panel}

            Beschreibung eingeben
            jonah (Inactive) made changes -
            Link New: This issue relates to JSWCLOUD-10149 [ JSWCLOUD-10149 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 905713 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1549635 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow 20141014 [ 742971 ] New: JIRA Bug Workflow w Kanban v6 [ 905713 ]
            mtokar.adm made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 588089 ] New: GreenHopper Kanban Workflow 20141014 [ 742971 ]

              Unassigned Unassigned
              dbdcc8cf5f68 Torsten Kleiber
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: