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

Ticket Details: Agile - View on Board should show position in Spintlog/Back-log

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • 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.

      It would be helpfull to see in a ticket details, where the tickets is connected to (in running sprint or backlog etc.).
      Better would be to read next to that "View on Board" also the info itself. like: "Spint 20", "Backlog" etc.
      perfect would be also which ranking (e.g. "Pos 2 - Backlog").

      Currently you only see in the right (bottom): Agile "View on Board"
      If you click on it, the item will be shown in the planing or in the board.
      But you need to click to see.

          Form Name

            [JSWSERVER-9533] Ticket Details: Agile - View on Board should show position in Spintlog/Back-log

            As a part of the linked issue, we've added more information to the View Issue page regarding which future sprint an issue is a part of. You can also modify this information directly from View Issue (or anywhere the issue fields are editable).

            Regards,
            JIRA Agile Team

            Michael Tokar added a comment - As a part of the linked issue, we've added more information to the View Issue page regarding which future sprint an issue is a part of. You can also modify this information directly from View Issue (or anywhere the issue fields are editable). Regards, JIRA Agile Team

            James Rickards added a comment - - edited

            +1 from me.

            I would go further and request that sprint related information should be editable.
            Tasks such as

            • Remove from Sprint
            • Add to Sprint
            • Add to unstarted Sprint

            We run with con-current sprints, and have many 20+ planned sprints on our backlog.

            The use case is

            1. jira sends out an e-mail to the PM (e.g. maybe someone used the mention in a comment)
            2. pm opens the ticket from the e-mail, and goes straight to the issue detail screen
            3. pm decides ticket must be descoped or added to a specific sprint
            4. pm currently has to click on 'view on board' then search through the backlog to find the ticket
              These extra task can be made far easier if it can be done directly from the issue.

            I do understand the motivation to goto the planning/work view, however this is clumsy and causes resistance among our PMs. They thus revert to using 'fixVersion' and queries to manage a program of work.

            Regards,

            James Rickards added a comment - - edited +1 from me. I would go further and request that sprint related information should be editable. Tasks such as Remove from Sprint Add to Sprint Add to unstarted Sprint We run with con-current sprints, and have many 20+ planned sprints on our backlog. The use case is jira sends out an e-mail to the PM (e.g. maybe someone used the mention in a comment) pm opens the ticket from the e-mail, and goes straight to the issue detail screen pm decides ticket must be descoped or added to a specific sprint pm currently has to click on 'view on board' then search through the backlog to find the ticket These extra task can be made far easier if it can be done directly from the issue. I do understand the motivation to goto the planning/work view, however this is clumsy and causes resistance among our PMs. They thus revert to using 'fixVersion' and queries to manage a program of work. Regards,

              Unassigned Unassigned
              b4129e9f9b81 MM (PREM)
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: