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

As a user I would like to see a notification for Issues that are blocked

    • 2
    • 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.

      As of now, it's easy to add an Issue to a Sprint and never realize that it's being blocked by another one. It would be handy if:

      • blocked Issues had a notifying icon on their card (as in Classic Boards - GHS-48);
      • a note would be displayed then a blocked Issue is added to a Sprint, reminding the user that they might want to resolve the blocking one first.

          Form Name

            [JSWSERVER-9039] As a user I would like to see a notification for Issues that are blocked

            Atlassian Update - 24 March 2025

            Hello,

            Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself.

            Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap.

            Please note the comments on this thread are not being monitored.

            You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here.

            To learn more about our recent investments in Jira Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues, current work, and future plans.

            Kind regards,
            Jira Data Center

            Aakrity Tibrewal added a comment - Atlassian Update - 24 March 2025 Hello, Thank you for submitting this suggestion. We appreciate you taking the time to share your ideas for improving our products, as many features and functions come from valued customers such as yourself. Atlassian is committed to enhancing the security and compliance of our Data Center products, with an emphasis on sustainable scalability and improving the product experience for both administrators and end-users. We periodically review older suggestions to ensure we're focusing on the most relevant feedback. This suggestion is being closed due to a lack of engagement in the last four years , including no new watchers, votes, or comments. This inactivity suggests a low impact. Therefore, this suggestion is not in consideration for our future roadmap. Please note the comments on this thread are not being monitored. You can read more about our approach to highly voted suggestions here and how we prioritize what to implement here. To learn more about our recent investments in Jira Data Center, please check our public roadmap and our dashboards, which contain recently resolved issues , current work, and future plans. Kind regards, Jira Data Center

            For your first point, you can use our new Flagging feature to visually indicated issues which are blocked. See the documentation for more information.

            Michael Tokar added a comment - For your first point, you can use our new Flagging feature to visually indicated issues which are blocked. See the documentation for more information.

            I was more interested in having order between blocking-related tasks preserved when I move them up and down in the Plan view.
            I'd find it convenient if, when B is blocked by A, GreenHopper kept A before B when I move B up and kept B after A when I moved A down.

            Dominic Herity added a comment - I was more interested in having order between blocking-related tasks preserved when I move them up and down in the Plan view. I'd find it convenient if, when B is blocked by A, GreenHopper kept A before B when I move B up and kept B after A when I moved A down.

              Unassigned Unassigned
              dwierzbicka Dobroslawa Wierzbicka (Inactive)
              Votes:
              9 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: