We recently upgraded from JIRA 5.X to JIRA 6.0.6, and are currently running Greenhopper 126.96.36.199.
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.
Thanks, Ronny, we'll give that a shot. What's confusing is that the tickets are now appearing in what seems to be random spots. At first I thought it was at the top of the first non-active sprint, but now I'm seeing them show up in the middle of the backlog, in the middle of inactive sprints, and I can't determine what the logic is. Quite strange...
...PermissionsStartOnly=true User=www-data Group=www-data ExecStart=/opt/jira/bin/startup.sh ExecStop=/opt/jira/bin/shutdown.sh TimeoutStartSec=120 TimeoutStopSec=600 PrivateTmp=true [Install] WantedBy...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs