In Jira Agile when should I use a "Story" and when should I use an "Improvement"

We just started using Jira (with the Jira Agile plugin - Scrum template) for our issue tracker and agile planning.

I am confused about the difference (or intended difference) between story and improvement. All our "stuff" is written as stories. Those stories describe both new functionality and improvements to existing functionality. Should those all be listed as a Story or should the improvements be listed as an Improvement?

I think we should keep things simple and just have Epic, Story, Bug; howev开发者_如何学Cer, I don't want to hide Improvement and end up with some unintended effects or end up missing useful functionality.

Thanks in advance for your advice.

We use "improvement" for functionality improvements in user stories delivered in previous sprints. In other words we use "story" for new user centric functionality and "improvement" for functionality improvements of current features and non-user centric functionality.

hope it helps

Just as an addition to a previous answer I would also suggest to add a new JIRA issue linking e.g. "improvements"-"is improvement of" so that every time you add an improvement you can link it with related story with this link. This will allow you to track how particular functionality was changing over the time when the amount of stories and improvements will significantly increase.