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

Delete "you can resolve or close this issue instead" text not accurate

      Trying to delete an issue currently shows an alert that ends:  

      "> If you're not sure, you can resolve or close this issue instead."

      However, there is no way to "close" an issue on next-gen project – or at least, no two ways to finish an issue. In each project, an issue can only be resolved a single way, whatever the last column on the board is, is the resolution status.  

      Therefore, this alert should read something like, "If you're not sure, you can resolve this issue instead." 

      (This is a deliberate choice apparently, https://community.atlassian.com/t5/Next-gen-questions/How-do-you-resolve-or-close-an-issue-in-a-next-gen-project/qaq-p/1050600 While I think that only one way to resolve an causes problems, especially with issue statistics, fixing the copy will prevent others from looking for how to "close" an issue from the delete alert text, when there is only a single alternative to deletion. This ticket is only about the delete alert text being not accurate about the 1 single alternative to deleting.)

      Steps to reproduce

      1. In a company-managed or team-managed project, click on an issue and click on the three dots [...] > Delete
      2. Observe the error message
         

        Delete JCK-14?
        You're about to permanently delete this issue, its comments and attachments, and all of its data.

        If you're not sure, you can resolve or close this issue instead.


          Form Name

            [JRACLOUD-92738] Delete "you can resolve or close this issue instead" text not accurate

            Fun fact, this project has a Closed state and no Done

            Frode Nilsen added a comment - Fun fact, this project has a Closed state and no Done

            Atlassian Update - October 16, 2024

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.

            Thank you again for providing valuable feedback to our team!
            Jira Cloud team

            Matthew Hunter added a comment - Atlassian Update - October 16, 2024 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know. Thank you again for providing valuable feedback to our team! Jira Cloud team

              Unassigned Unassigned
              b9ec29ccdfa6 Mike Sanderson
              Affected customers:
              5 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: