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

Provide option to only clone open subtasks when cloning an issue

XMLWordPrintable

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

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

      When you clone a task and want to also clone the subtasks, I'd like an option to only clone the open/incomplete subtasks. We usually clone when a release is done, but some subtasks are incomplete and need to be moved to another release.

            [JRACLOUD-14236] Provide option to only clone open subtasks when cloning an issue

            Roy Krishna (Inactive) added a comment -

            Hi,

            This is a bulk update to specific issues in the JIRA (JRA) project

            As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today.

            Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com

            If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close.

            Best regards
            Roy Krishna and Josh Devenny
            JIRA Product Management

            Roy Krishna (Inactive) added a comment - Hi, This is a bulk update to specific issues in the JIRA (JRA) project As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today. Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close. Best regards Roy Krishna and Josh Devenny JIRA Product Management

            Bob Swift added a comment -

            Yes, unresolved would seem to be the most appropriate way to classify them.

            Bob Swift added a comment - Yes, unresolved would seem to be the most appropriate way to classify them.

            AntonA added a comment -

            We do not usually do things based on status. I guess we could allow to clone only unresolved sub-tasks.

            AntonA added a comment - We do not usually do things based on status. I guess we could allow to clone only unresolved sub-tasks.

              Unassigned Unassigned
              bob.swift Bob Swift
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: