Uploaded image for project: 'Xporter for Jira'
  1. Xporter for Jira
  2. XPORTER-488

Improvement the way how Issue fields are loaded by using a lazy load mechanism

    XporterXMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • Release 3.4.0
    • 5.0.0
    • Document Engine
    • None
    • R5.0.0 Sprint 4, R5.0.0 Sprint 5
    • UNCOVERED

    Description

      The mais goal of this improvement is to reduce the memory usage at runtime and improve the Xporter performance.

      This story is composed by 2 parts:

      1. When a template is created/updated, all fields should be extracted and saved on database.
      2. Fieldmapper should receive these fields and must load only these fields when the mapping is being created.

      Note: It's necessary to create a migration task to extract all fields from templates already installed.

      Attachments

        Issue Links

          There are no Sub-Tasks for this issue.

          Activity

            People

              rmbr Rui Rodrigues
              rmbr Rui Rodrigues
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 2 weeks Original Estimate - 2 weeks
                  2w
                  Remaining:
                  Time Spent - 2 weeks, 4 days, 5 hours, 20 minutes Remaining Estimate - 1 week, 1 day, 40 minutes
                  1w 1d 40m
                  Logged:
                  Time Spent - 2 weeks, 4 days, 5 hours, 20 minutes Remaining Estimate - 1 week, 1 day, 40 minutes
                  2w 4d 5h 20m