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

A tooltip with the full text of the Sprint Goal isn't shown when accessing the Backlog of a Scrum Project

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low (View bug fix roadmap)
    • None
    • 8.8.0, 8.9.0, 8.10.0, 8.11.0, 8.12.0, 8.13.0, 8.14.0, 8.15.0, 8.16.0, 8.17.0, 8.18.0, 8.19.0, 8.20.0, 8.21.0, 8.22.0
    • Scrum Board, Sprint
    • None

      Issue Summary

      Accessing the Active Sprints board of a Scrum project, if the Sprint Goal text is too large, then a user can hover the mouse over the goal for a tooltip that will show more of that text.

      When a user access the Backlog board, the Sprint Goal is also trimmed if the text is too large.
      However, the tooltip isn't available since Jira Software 8.8.0.

      Users won't be able to read the full Sprint Goal text from the Backlog board if the text is lengthy.

      Steps to Reproduce

      1. Install a vanilla Jira Software instance.
        • The issue started on version 8.8.0 and was validated on 8.22.0 as well.
      2. Create a Scrum Project with sample data.
      3. Access the Backlog of that project.
      4. Edit the active Sprint.
      5. Add a lengthy text as the Sprint goal and save it.
      6. Still on the Backlog board, hover the mouse over the Sprint Goal.

      Expected Results

      A tooltip is shown with the full text of the Sprint Goal.

      Actual Results

      Nothing is shown to the user.
      Users without the Edit Sprint permissions won't be able to read the full text of the Sprint Goal from the Backlog board.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available.

        1. screenshot-1.png
          screenshot-1.png
          546 kB
        2. screenshot-2.png
          screenshot-2.png
          478 kB
        3. screenshot-3.png
          screenshot-3.png
          755 kB

          Form Name

            [JSWSERVER-21296] A tooltip with the full text of the Sprint Goal isn't shown when accessing the Backlog of a Scrum Project

            SET Analytics Bot made changes -
            UIS Original: 5 New: 0
            SET Analytics Bot made changes -
            UIS New: 5
            SET Analytics Bot made changes -
            Support reference count Original: 1 New: 2
            SET Analytics Bot made changes -
            Support reference count New: 1
            Bugfix Automation Bot made changes -
            Introduced in Version Original: 8.8 New: 8.08
            Stasiu made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Stasiu made changes -
            Introduced in Version Original: 8.08 New: 8.8
            Bugfix Automation Bot made changes -
            Introduced in Version New: 8.08
            Thiago Masutti made changes -
            Link New: This issue is related to JSWSERVER-16161 [ JSWSERVER-16161 ]
            Thiago Masutti made changes -
            Description Original: A tooltip with the full text of the Sprint Goal isn't shown when accessing the Backlog of a Scrum Project

            h3. Issue Summary
            Accessing the Active Sprints board of a Scrum project, if the Sprint Goal text is too large, then a user can hover the mouse over the goal for a tooltip that will show more of that text.


            When a user access the Backlog board, the Sprint Goal is also trimmed if the text is too large.
            However, the tooltip isn't available since Jira Software 8.8.0.

            Users won't be able to read the full Sprint Goal text from the Backlog board if the text is lengthy.

            h3. Steps to Reproduce
             # Install a vanilla Jira Software instance.
              #* The issue started on version 8.8.0 and was validated on 8.22.0 as well.
             # Create a Scrum Project with sample data.
             # Access the Backlog of that project.
             # Edit the active Sprint.
             # Add a lengthy text as the Sprint goal and save it.
             # Still on the Backlog board, hover the mouse over the Sprint Goal.


            h3. Expected Results
            A tooltip is shown with the full text of the Sprint Goal.

            h3. Actual Results
            Nothing is shown to the user.
            Users without the _Edit Sprint_ permissions won't be able to read the full text of the Sprint Goal from the Backlog board.


            h3. Workaround

            _Currently there is no known workaround for this behavior. A workaround will be added here when available._
            New: h3. Issue Summary
            Accessing the Active Sprints board of a Scrum project, if the Sprint Goal text is too large, then a user can hover the mouse over the goal for a tooltip that will show more of that text.
             !screenshot-1.png|thumbnail!

            When a user access the Backlog board, the Sprint Goal is also trimmed if the text is too large.
            However, the tooltip isn't available since Jira Software 8.8.0.
             !screenshot-2.png|thumbnail!

            Users won't be able to read the full Sprint Goal text from the Backlog board if the text is lengthy.

            h3. Steps to Reproduce
             # Install a vanilla Jira Software instance.
              #* The issue started on version 8.8.0 and was validated on 8.22.0 as well.
             # Create a Scrum Project with sample data.
             # Access the Backlog of that project.
             # Edit the active Sprint.
             # Add a lengthy text as the Sprint goal and save it.
             # Still on the Backlog board, hover the mouse over the Sprint Goal.


            h3. Expected Results
            A tooltip is shown with the full text of the Sprint Goal.
             !screenshot-3.png|thumbnail!

            h3. Actual Results
            Nothing is shown to the user.
            Users without the _Edit Sprint_ permissions won't be able to read the full text of the Sprint Goal from the Backlog board.


            h3. Workaround

            _Currently there is no known workaround for this behavior. A workaround will be added here when available._

              Unassigned Unassigned
              tmasutti Thiago Masutti
              Affected customers:
              3 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated: