GeezerVison

Changes:

• provided ability to handle package annotations
• add package target to Epic(s), Feature(s), Flaky, Issue(s), Link(s), Muted, Owner, Severity, Story(es), TmsLink(s)

The article about package level annotations and package-info files

Context

Sometimes it has to do a lot of work

• mark many classes or methods with annotations
• check the relevance of the labels in the code in case of changes

I don't think that the creating a base class with necessary labels for further extending by tests classes is a good solution (personally, I think it's an anti-pattern). It's much easier to mark packages and put tests there and to add additional marks (to classes and methods) only if it is necessary