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

Set a default Status when moving tickets to a different project

XMLWordPrintable

    • 2
    • 4

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

      It would be great if the status of the issue will be automatically mapped when moving to a different project. Hence, setting a default value will be great,

            [JRACLOUD-39752] Set a default Status when moving tickets to a different project

            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-5159 – Allow Admin to force set target status for all 'Move Issue' operations / ability to set a default status 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-5159 – Allow Admin to force set target status for all 'Move Issue' operations / ability to set a default status 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.

            Greg Williams added a comment -

            I looked at this search result for a similar issue but for Jira Server and using that was able to determine that this is not a feature we can employ in Jira Cloud.

            It appears that the system ID of the status dictates the placement of the status in the workflow (when viewing by text) where the lower the ID #, then the higher it is placed. The status at the top of the text-based step is thus the "default".

            I had a user wanting to change the default status to a different one. The only way I can see that happening is to delete the status from the project and even further, deleting the status from the tenant and re-creating it, which of course would affect any other project using the status, which is a headache I'd rather avoid.

            If this is still under consideration for future development it would be a nice (albeit subtle) improvement. Thanks

             

            Greg Williams added a comment - I looked at this search result for a similar issue but for Jira Server and using that was able to determine that this is not a feature we can employ in Jira Cloud. It appears that the system ID of the status dictates the placement of the status in the workflow (when viewing by text) where the lower the ID #, then the higher it is placed. The status at the top of the text-based step is thus the "default". I had a user wanting to change the default status to a different one. The only way I can see that happening is to delete the status from the project and even further, deleting the status from the tenant and re-creating it, which of course would affect any other project using the status, which is a headache I'd rather avoid. If this is still under consideration for future development it would be a nice (albeit subtle) improvement. Thanks  

              Unassigned Unassigned
              acardino Anna Cardino (Inactive)
              Votes:
              11 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: