We recently upgraded from JIRA 5.X to JIRA 6.0.6, and are currently running Greenhopper 6.2.5.1.
After this upgrade, whenever someone creates a new ticket, it is automatically sent to the top of the first non-active sprint in Greenhopper. This is a huge concern for us, as we rely heavily on the prioritization & ordering in Greenhopper to determine the next dev work. Given that our client also shares access to our JIRA instance, we are worried that newly submitted tickets will be confused as the most important item to work on, unless someone moves it to the appropriate location.
I would like to know how we can revert back to sending all newly created tickets to the bottom of the product backlog.
