Package com.atlassian.greenhopper.customfield.epiclink

Class EpicLinkHistoryEntryFactory

java.lang.Object
com.atlassian.greenhopper.customfield.epiclink.EpicLinkHistoryEntryFactory
@Service public class EpicLinkHistoryEntryFactory extends Object
Encapsulates the logic of creating epic history entries from either a lucene document or an issue

  • Constructor Details

    • EpicLinkHistoryEntryFactory

      @Autowired public EpicLinkHistoryEntryFactory(com.atlassian.jira.issue.changehistory.ChangeHistoryManager changeHistoryManager, com.atlassian.jira.i18n.terminology.TerminologyEntryReader terminologyEntryReader)

  • Method Details

    • getEpicChangeHistory

      public EpicLinkHistoryData getEpicChangeHistory(com.atlassian.jira.issue.Issue issue, com.atlassian.jira.issue.fields.CustomField epicLinkCustomField)
      Get the Epic change history for a given issue. This method takes into account possibly assigned epic links at issue creation time. Do not treat sub-tasks differently - they are never associated with an epic

      An epic history of an issue is based on change items. Change items store information which field has been changed and its previous and current values.

      As change items identify a field by its translated name rather than id, changing or translating a field results in storing change items with different names. For this reason, finding a whole change history for an issue and a particular custom field requires querying for change items using all its previous translations or names.

      The above applies to the Terminology feature, since it uses the translations mechanism for renaming the Epic Link custom field.