Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-1001

Allow unassigned issues on a per-project basis

XMLWordPrintable

    • 4
    • 15

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    • Hide
      Atlassian Update – 26 August 2024

      Hi everyone,

      Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users, and we understand that this is an important issue to many. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that this is not a priority for the immediate future.

      Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.

      We understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions or feedback.

      Regards,
      Saskia van der Peet

      svanderpeet@atlassian.com
      Product Manager, Jira Cloud

      Show
      Atlassian Update – 26 August 2024 Hi everyone, Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users, and we understand that this is an important issue to many. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that this is not a priority for the immediate future. Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog. We understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions or feedback. Regards, Saskia van der Peet svanderpeet@atlassian.com Product Manager, Jira Cloud

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Atlassian Update - 23 April 2015

      Hi everyone,

      Thanks for voting and commenting on this issue. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with JIRA.

      This suggestion is a priority for the JIRA development team, but I am not able to provide an accurate estimate for when this will be resolved. We will update this issue as soon as we can confidently project a release.

      Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Dave Meyer
      dmeyer@atlassian.com
      Product Manager, JIRA Platform

      Some of our project members are rumbling about having to assign issues, when on some of the other projects this is important. It seems this (along with some other options, such as mailing and voting) would make more sense as an option on the project rather than on the whole server.

            [JRACLOUD-1001] Allow unassigned issues on a per-project basis

            Saskia added a comment -
            Atlassian Update – 26 August 2024

            Hi everyone,

            Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future.

            Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.

            We understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions or feedback.

            Regards,
            Saskia van der Peet

            svanderpeet@atlassian.com
            Product Manager, Jira Cloud

            Saskia added a comment - Atlassian Update – 26 August 2024 Hi everyone, Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future. Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog. We understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions or feedback. Regards, Saskia van der Peet svanderpeet@atlassian.com Product Manager, Jira Cloud

            Aleksi Leinonen added a comment -

            Can't believe this is still unresolved.

            Aleksi Leinonen added a comment - Can't believe this is still unresolved.

            Tom Heitbrink added a comment -

            Would have made a lot more sense if it was assigned to the Jira backlog user, right ? I'm also in the process of moving away from unassigned as a user, since it is not even a user.
            In some cases tickets were at a later moment assigned to an unassigned user, and became lost, as they were not seen anymore by the team that should have solved it.
            And where I can understand the idea behind it "it is not assigned to a user", it is assigned to something.
            In most cases it's assigned to a queue, and in some cases it's waiting to be dispatched within a team.
            The difference ?
            Dispatch should always contain only recent items, where the backlog contains items you only want to look at when a new workload can be provided.

            So the workaround I'm taking is that wherever applicable, I'm creating a backlog and a dispatch user.
            The items assigned to these users are in the dashboards of the team that should assign the tickets when ready to be picked up.
            I think Atlassian's better option might be a recommendation on how to avoid the unassigned alltogether, for those like me.
            The rest can then keep the unassigned issues.

            Tom Heitbrink added a comment - Would have made a lot more sense if it was assigned to the Jira backlog user, right ? I'm also in the process of moving away from unassigned as a user, since it is not even a user. In some cases tickets were at a later moment assigned to an unassigned user, and became lost, as they were not seen anymore by the team that should have solved it. And where I can understand the idea behind it "it is not assigned to a user", it is assigned to something. In most cases it's assigned to a queue, and in some cases it's waiting to be dispatched within a team. The difference ? Dispatch should always contain only recent items, where the backlog contains items you only want to look at when a new workload can be provided. So the workaround I'm taking is that wherever applicable, I'm creating a backlog and a dispatch user. The items assigned to these users are in the dashboards of the team that should assign the tickets when ready to be picked up. I think Atlassian's better option might be a recommendation on how to avoid the unassigned alltogether, for those like me. The rest can then keep the unassigned issues.

            Teodor CAPH added a comment -

            Funny thing, this ticket is assigned to Unassigned!

            Teodor CAPH added a comment - Funny thing, this ticket is assigned to Unassigned!

            Deleted Account (Inactive) added a comment -

            Agreed this issue has become very popular now and we have a wide range of projects that are split on this - So having this on per project basis would be ideal.

            Deleted Account (Inactive) added a comment - Agreed this issue has become very popular now and we have a wide range of projects that are split on this - So having this on per project basis would be ideal.

            Andrew Erickson added a comment -

            Any update on this? It's been 4 years... It would be nice to not have to create 'nobody' users to accommodate this functionality.

            Andrew Erickson added a comment - Any update on this? It's been 4 years... It would be nice to not have to create 'nobody' users to accommodate this functionality.

            Dylan Etkin [Atlassian] added a comment -

            Hi Amrita,
            We do not currently have an ETA on this feature. If you would like to understand how we decide which features will be implemented then you can read about it here.
            Thanks,
            Dylan

            Dylan Etkin [Atlassian] added a comment - Hi Amrita, We do not currently have an ETA on this feature. If you would like to understand how we decide which features will be implemented then you can read about it here . Thanks, Dylan

            Amrita Dhillon added a comment -

            Team: do you have an ETA on when this request will be implemented?

            Amrita Dhillon added a comment - Team: do you have an ETA on when this request will be implemented?

            Neal Applebaum added a comment -

            Denis, I guess you're using external user mgmt, then. I don't. So it hasn't been a big problem for me.

            Neal Applebaum added a comment - Denis, I guess you're using external user mgmt, then. I don't. So it hasn't been a big problem for me.

            Denis Yurkin added a comment -

            Neal, that may work until you have all your JIRA users presented in domain (and no users in JIRA allowed except existing in domain). This is exactly our case, hence I woudl vote for the original bugreport.

            Denis Yurkin added a comment - Neal, that may work until you have all your JIRA users presented in domain (and no users in JIRA allowed except existing in domain). This is exactly our case, hence I woudl vote for the original bugreport.

              Unassigned Unassigned
              8397740ea872 Michael Phillimore-Brown
              Votes:
              135 Vote for this issue
              Watchers:
              65 Start watching this issue

                Created:
                Updated:
                Resolved: