-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
6
-
Severity 2 - Major
-
Summary
Issues with Story Issue Types missing from boards, and removed from all Issue Type Scheme. This happened after creating a "Simplified" Project
Steps to Reproduce
- Create a simplified project
- Go back to your board
Expected Results
- Issues with Story issue types still remains on the board
- Story issue type is still associated on the project's Issue Type Scheme
Actual Results
- Issues with Story issue types are missing from the board
- Story issue type is no longer associated on the project's Issue Type Scheme
Notes
- The root cause of this issue has been fixed for now, however we are still working on the fix for Story issue type that has been disassociated from the Issue Type Scheme
- By default, Story issue type should be associated to all "Software" type project
- Therefore, we will associate Story issue type to Issue Type Schemes of "Software" type projects
Workaround
The manual workaround at the moment would be:
- Proceed to your project's settings
- Click the "Issue types" menu on the sidebar
- Click on the "Actions" button > "Edit issue types"
- Drag the "Story" from "Available Issue Types" to "Issue Types for Current Scheme"
- Click on the save button
Or alternatively, you can also
- Proceed to the Issue Type Schemes page in Jira Administration:
- https://<your_site>.atlassian.net/secure/admin/ManageIssueTypeSchemes!default.jspa
- Look for your project, and click "edit"
- Drag the "Story" from "Available Issue Types" to "Issue Types for Current Scheme"
- Click on the save button
Yes this isn't cool. We are still having issues today since experience this issue on Friday 13 2018. We didn't have nearly as many projects as Vinay but it was still annoying. Our default issue scheme still can't even have stories and bugs added to it which is strange.
I also had a problem today where sprints stopped working properly. I had multiple teams where all their assigned sprints lost the work associated with them. The only way to fix it was to assign a the default field configuration manually... which happens to be the only one we have.... so I have no idea why this resolved the issue... but it did.