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

Hover over Issue Link to show Issue Summary

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Tracked Elsewhere
    • None
    • None
    • Standalone
    • 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.

      When hovering over an Issue Link, rather than seeing just:

      View this issue in Jira: XX-NNNN

      You should see

      Jira: XX-NNNN 'Summary text'

      IF this was implemented across the board then many of the reports will be instantly more useful as you then don't have to navigate to different pages to see what ID XX-NNNN refers to.

      A task ID on its own is much less useful in Agile development than it is in the Support environment. In Support the ID is often used as the basis for referring to a customer problem or ticket.

      However, in Agile, the story summary is the main thing and IDs are more incidental.

            [JSWSERVER-6819] Hover over Issue Link to show Issue Summary

            Martin (Inactive) added a comment -

            This will be tracked in stories for each type of report.

            Martin (Inactive) added a comment - This will be tracked in stories for each type of report.

            Shaun Clowes (Inactive) added a comment -

            Hi Andreas,

            This is a good idea but it's not an implementable story since we'd actually need to modify each chart to work this way (i.e. the story is too big and would be delivered as multiple individual stories). There is already a story for a description on hover on the burndown chart in the backlog, but if you're looking for other summaries on hover I'd recommend opening separate stories for each.

            Thanks,
            Shaun

            Shaun Clowes (Inactive) added a comment - Hi Andreas, This is a good idea but it's not an implementable story since we'd actually need to modify each chart to work this way (i.e. the story is too big and would be delivered as multiple individual stories). There is already a story for a description on hover on the burndown chart in the backlog, but if you're looking for other summaries on hover I'd recommend opening separate stories for each. Thanks, Shaun

              Unassigned Unassigned
              andreaswalsh Andreas Walsh
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: