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

when we have story points with floating points - like 3.5 or the like the value get truncated

    • Icon: Suggestion Suggestion
    • Resolution: Support Request
    • None
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      we are using values like 3.5 in our story point field and sometimes they appear and sometimes not. So when we edit the story is shows the 3.5.
      in the issue the 3.5 is truncated to 3 when displayed. when displayed in the
      Rapid release board it shows 3.5. when it is exported to excel it is a 3.

      this is a major problem for us how can it be fixed?

      I have attached slides showing the different screens

      Janeen

        1. SnapShot_130516_102749.jpg
          SnapShot_130516_102749.jpg
          281 kB
        2. SnapShot_130516_102801.jpg
          SnapShot_130516_102801.jpg
          294 kB
        3. SnapShot_130516_102833.jpg
          SnapShot_130516_102833.jpg
          421 kB

            [JSWSERVER-8836] when we have story points with floating points - like 3.5 or the like the value get truncated

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3069340 ] New: JAC Suggestion Workflow 3 [ 3659303 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2626415 ] New: JAC Suggestion Workflow [ 3069340 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2326470 ] New: Confluence Workflow - Public Facing v4 [ 2626415 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2043264 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2326470 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2031375 ] New: JIRA PM Feature Request Workflow v2 [ 2043264 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 736275 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2031375 ]

            I have the exact same problem right now... what is the solution?

            Olivier Voyer added a comment - I have the exact same problem right now... what is the solution?
            Martin (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 531531 ] New: JIRA PM Feature Request Workflow v2 [ 736275 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Major [ 3 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Michael Tokar made changes -
            Resolution New: Support Request [ 18 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Hi,
            Thanks for your feedback on JIRA Agile.
            Could you please create a support ticket at https://support.atlassian.com? That way we can provide you with support specific to your circumstances and with higher security.
            Regards,
            JIRA Agile Team

            Michael Tokar added a comment - Hi, Thanks for your feedback on JIRA Agile. Could you please create a support ticket at https://support.atlassian.com? That way we can provide you with support specific to your circumstances and with higher security. Regards, JIRA Agile Team

              Unassigned Unassigned
              ff9e3b05736f Janeen Kedzierski
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: