Typically this problem seems to affect new user stories recently added since the sprint was crated and populated.
Refreshing the page fixed this.
As a product owner working with product backlogs, I usually work with three levels of specification: Themes, Epics and User Stories. This a very common way to structure a product backlog.
So, it would be great to be able to start a backlog only with Themes and Epics, and as the project evolves through backlog grooming of prioritized Epics, User Stories would start to be written.
I develop an open source project and want to make the backlog available to all interested users of the software. For that a read-only version of the backlog that can be read without login would be great.
That's an interesting idea Daniel. We've not had many people ask for this to date. You could achieve this using our API, however this would of course require some development work on your end. We'll consider the idea, however quite honestly unless more people ask for it it will be low on our priority list.
Thanks for the suggestion.
Would it help if you could just print individual stories as that may be easier & quicker to implement, or do you think that would not really solve the problem as you need to print a few stories in a batch? The problem with printing one at a time is it would be quite a waste of paper.
- Setup development environment
- Install Software
- etc etc
Customer support service by UserEcho