versioning - JIRA: Epic issue that can last for multiple versions and "Affect versions"&"Fix versions" fields -
I have a project. It is a web site, the project has just begun. I found it appropriate to group all design related stories in an epic called "Design" ...
But ... I started right now " To fill the design "EPIC GIARA card, I did not believe myself how I can handle more editions than epic (especially by seeing the" Effects version "and" Fix version "field). Problem: Personally, I think the latter option is better, but I want to hear about your thoughts. I will separate the design epic in smaller subjects, which will allow easy planning per edition. For example, you can make an epic for the header and keep all the stories needed to design and develop this header. I advise against putting everything in an epic version needs to show that what was released on that date. After the episode of an epic period, you will be confused to see which release you have released. Here's the definition of cumin: One version is a set of features and fixes that have been released as a single update of your product. Allocating issues in the versions helps you plan the order in which new features (stories) for your product will be released to your customers.
Comments
Post a Comment