-
Suggestion
-
Resolution: Low Engagement
Issue Summary
When moving issues to a next-gen project, when mapping the statuses to the destination project there is no displaying logical order, as you can see it below:
Next-gen workflow/columns:
Steps to Reproduce
- Bulk move issues;
- Select a next-gen project as a destination;
- When mapping statuses, open the box to select the new status;
Expected Results
Display in the order of the workflow/columns or with the status that has the same name from the source project.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
Hi everyone,
Thank you for bringing this suggestion to our attention.
As explained in our new features policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team!