Issues with type "bug" are not visible in BackLog list on GreenHopper Scrum Board Plan view.
Agile project management for Kanban and Scrum software development powered by Atlassian GreenHopper (v6.0.1)
Bug tracking and project tracking for software development powered by Atlassian JIRA (v5.1.2#773-sha1:b805b97)
Okay, thanks for pointing me to right direction. Problem was not issue type fields it was the custom "View Field Configuration" attached to Bug issues. Now Rank and Sprint fields are visible in the view configuration and Bugs are displayed on Sprint Plannign view.
I encountered the same problem on an instance. The tips over here where a good start. By double checking the effective stored data in the database, I was able to fix The Problem.
By default, the Sprint field is configured to be applied to Epics, Stories, Tasks and Sub-tasks. When you create a new Bug, this custom field will not be added to the issue in the database. You can check this by searching with JQL:
"project=MY_PROJECT AND issueType=Bug AND Sprint is EMPTY"
"project=MY_PROJECT AND issueType=Bug AND Sprint is not EMPTY"
Will return the bugs.
To fix this, be sure that you add the Sprint field to your issue type. Do this by going to the "Custom Fields" page in your administration (http://yourjirainstance/secure/admin/ViewCustomFields.jspa).
Here, go to the Sprint custom field, click the Cog icon on the right and select "Configure".
On this page, you can see if the field is configured for your Bug issue type. If this is not the case, click next to "Applicable contexts for scheme" on "Edit Configuration". On this page, cmd/ctrl click in the list to select the Bug issue as well and hit Modify.
You now fixed the problem for all the new bugs that are created. For the existing bugs, we'll need to add the Sprint custom field. To do this, we'll perform a bulk change.
By now, you should see your bugs showing up in your Rapid Board.
I have (maybe exacty) the same problem - try opening the bug issues to edit mode and save them without changing anything. Do they appear now? If yes, you got the same problem as me (I already filed a support ticket)
Seems to have something do do with indexing and creating a new board/filter combination...
...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