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

Selecting parent task when converting to sub-task or changing the parent's task does not list down issues

      Issue Summary

      When an issue is converted to sub-task, or when a sub-task needs to change its parent's task, "Select Parent Issue" field will not list down issues as you key in number of text, unless they're in the "History Search".

      Steps to Reproduce

      1. Create two issues
      2. Convert one of the issues to sub-task
      3. In the convert screen, in "Select Parent Issue" field, key in an issue number or part's of issue summary, that exist in the project

      Expected Results

      It would list down possible issues.

      Actual Results

      It will only list down possible issues if we have search for the issues before because those would be in "History Search", if not nothing happen.

      Workaround

      Need to key in the exact issue key.

            [JRACLOUD-78190] Selecting parent task when converting to sub-task or changing the parent's task does not list down issues

            Atlassian Update - January 12, 2023

            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 - January 12, 2023 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
              rabdulghani Yanty Ghani (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: