-
Suggestion
-
Resolution: Unresolved
-
927
-
67
-
Atlassian Update 23 Sep 2024
*Yousef Abusamak, Product Manager in Jira*
Thank you all for your continued feedback and engagement on this issue. We truly understand how important this feature is to many of you and how it would positively impact your workflows. At this stage, I want to share that while we acknowledge the demand, this feature is not currently on our roadmap.
That said, we are always assessing priorities and evolving our plans based on customer needs. Your feedback plays a crucial role in helping us shape the future of Jira, and we encourage you to continue sharing your thoughts. We deeply appreciate your patience and understanding as we strive to balance the wide range of requests from our diverse user base.
Thank you again for your ongoing support of Jira. We remain committed to enhancing the product and delivering value to all of you.
-------------
Atlassian Update 09 Aug 2023
Hi Everyone,
This is Prerna Rao from the Jira Platform team.
Thank you for all the comments on this request to change issue type schemes for projects with large number of issues..
Currently, this operation relies on Bulk Move. Bulk Move currently supports moving only 1000 issues at a time. This limitation has been called out in this documentation:
Editing multiple Issues
We are moving this to a feature request for our long term roadmap. Supporting movement of over 1000 issues at a time requires an architectural change. Your existing votes will carry over and help with prioritisation decisions. Please continue to track our progress using this ticket.
Issue Summary
Not possible to change/migrate projects to another Issue type Scheme
Steps to Reproduce
- Open https://_yoursitehere_.atlassian.net/plugins/servlet/project-config/<ProjectKey>/summary
- Select Issues -> Type
- Action -> Use a different scheme
- Select new scheme -> <Selected Scheme>
- Select the new issue type to migrate issues
- Next button -> Wait for the timeout issue
Expected Results
Change the Project issue type scheme to a different scheme
Actual Results
Action is failing due to a timeout issue on the Proxy server due to a large number of issues to be bulk moved to a new issue type.
Checking a HAR file we can see the following entries:
Request URL: https://_yoursitehere_.atlassian.net/secure/admin/MigrateIssueTypes!chooseContext.jspa Request Method: POST Status Code: 504 Remote Address: X.X.X.X:443 Referrer Policy: strict-origin-when-cross-origin
<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html>
Workaround
Change the Issue Type by performing several bulk move operations on the affected issues before changing the issue Issue type scheme.