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

Provide the option to change the reporter when cloning issue

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • 17
    • 1
    • 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.

      Problem statement

      At the moment, when cloning an issue, the reporter of the cloned issue will follow the reporter of the original issue. It will need to be done manually if users would like to change the reporter to a different user.

      Suggestion

      It would great if JIRA could provide an option to change the reporter of the cloned issue before the operation - e.g:

      • Option 1: keep the reporter
      • Option 2: change to: current user / ________ (user picker field)

            [JRACLOUD-65004] Provide the option to change the reporter when cloning issue

            Atlassian Update - August 2023

            After some analysis, we've found that this ticket is a duplicate of the request JRACLOUD-5052 – Allow different "Clone Issue" options which has more votes.

            We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment - Atlassian Update - August 2023 After some analysis, we've found that this ticket is a duplicate of the request JRACLOUD-5052 – Allow different "Clone Issue" options which has more votes. We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            I am also looking at this feature at my company. I am not an admin, but so many clone issues, and the reporter gets set to the same. Often they follow up by asking what the ticket is for which creates confusion and a waste of people's time.

             

            I am all for either, the ability to set, or, just make the reporter the same as the one that's closing. Do both, and keep the ability to update this on the fly for certain roles and other lower roles, just auto-update.

            Nick Cothran added a comment - I am also looking at this feature at my company. I am not an admin, but so many clone issues, and the reporter gets set to the same. Often they follow up by asking what the ticket is for which creates confusion and a waste of people's time.   I am all for either, the ability to set, or, just make the reporter the same as the one that's closing. Do both, and keep the ability to update this on the fly for certain roles and other lower roles, just auto-update.

              Unassigned Unassigned
              nhassan Nur Asnida Hassan (Inactive)
              Votes:
              9 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: