-
Suggestion
-
Resolution: Timed out
-
None
-
0
-
6
-
NOTE: This suggestion is for JIRA Software Cloud. Using JIRA Software Server? See the corresponding suggestion.
Problem Definition
Currently, when moving the issue to another project also the Sprint information is copied
Suggested Solution
Customer is suggesting that the issue should be removed from Sprint automatically before moving it to another project
Workaround
remove issue from Sprint manually before moving the issue to another project
- is related to
-
JSWSERVER-15615 Remove issue from Sprint before moving it to another project
- Gathering Interest
Hi everyone,
Thank you for bringing this suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise 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 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 on 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 - Jira Cloud Product Management