A user story (or just a “story”) is a specific task within an epic written from the user perspective i.e. it does not define how it should be implemented. A story in then broken down in tasks/sub-tasks

Basically, an epic is one big piece of product functionality. Usually, it is too big to be completed in one sprint and should be split up into smaller bodies of work.

flags an issue that needs immediate resolution and "hot fix" on the production

represents an issue describing how an existing feature could be improved.

indicates an issue in a draft state ie an idea...that needs further work

issue needs review

the issue is ready for development/fix

the issue is mentioned in a MR and will be closed once MR is accepted

use when closing an issue that we decided not to fix